-
Notifications
You must be signed in to change notification settings - Fork 14
Set up Renovate #22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Set up Renovate #22
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,22 @@ | ||
| { | ||
| "$schema": "https://docs.renovatebot.com/renovate-schema.json", | ||
| "extends": ["config:best-practices"], | ||
| "schedule": ["* 0-4 * * 1"], | ||
| "timezone": "America/Los_Angeles", | ||
| "minimumReleaseAge": "30 days", | ||
| "packageRules": [ | ||
| { | ||
| "groupName": "Routine updates", | ||
| "matchUpdateTypes": ["minor", "patch", "pin", "digest"], | ||
| "automerge": true | ||
| }, | ||
| { | ||
| "matchUpdateTypes": ["major"], | ||
| "automerge": false | ||
| }, | ||
| { | ||
| "matchDepTypes": ["devDependencies"], | ||
| "automerge": true | ||
| } | ||
| ] | ||
| } | ||
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🌐 Web query:
In Renovate configuration, when multiple packageRules match the same dependency, how are conflicting fields like "automerge" resolved? Does a later broad rule (e.g., matchDepTypes=devDependencies) override an earlier matchUpdateTypes=major rule?💡 Result:
In Renovate configuration, when multiple packageRules match the same dependency, all matching rules are applied in array order to produce a single resulting config for that dependency/update. For each config option, if it is "mergeable" (typically arrays/objects), values from matching rules are merged (e.g., addLabels appends labels). If non-mergeable (e.g., booleans like automerge), the value from the last matching rule overrides previous ones. "automerge" is a boolean and thus non-mergeable (string types are always non-mergeable, and booleans behave similarly as scalars), so the last matching rule sets its value. A later broad rule (e.g., matchDepTypes=devDependencies) will override an earlier specific rule (e.g., matchUpdateTypes=major) for conflicting fields like automerge, because rules are applied sequentially and later ones override non-mergeable options.
Citations:
devDependenciesautomerge rule will override major-update protection due to rule precedence.This rule (lines 18-21) matches all devDependency updates and sets
automerge: true. In Renovate's packageRules, when multiple rules match the same dependency, non-mergeable fields likeautomergeuse the value from the last matching rule. Since this rule comes after the earlier"major"rule that setsautomerge: false, it will override that setting for major devDependency updates. Given that your devDependencies include high-impact packages (react,react-dom,openai,convex,typescript), auto-merging their major updates is risky.Add
"matchUpdateTypes": ["minor", "patch", "pin", "digest"]to this rule to explicitly exclude major updates, or move this rule before the major rule and adjust accordingly.🤖 Prompt for AI Agents