Configure Renovate to bump dependency ranges and run weekly#1241
Merged
Conversation
Copilot created this pull request from a session on behalf of
underfisk
May 27, 2026 15:17
View session
underfisk
approved these changes
May 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Renovate was effectively producing lockfile-only updates, which left dependency ranges in manifests unchanged. This change switches update behavior to keep
package.jsonand lockfile aligned, and tightens scheduling to a single weekly run.Renovate update strategy
rangeStrategytobumpso dependency updates modify manifest ranges (not just lockfile state).Renovate schedule
{ "schedule": ["before 4am on monday"], "timezone": "America/New_York", "rangeStrategy": "bump" }