chore(renovate): disable engines updates and remove automerge - #679
Merged
Conversation
jim-counter
force-pushed
the
chore/renovate-config-cleanup
branch
from
July 3, 2026 10:10
49fd740 to
7def1de
Compare
jim-counter
changed the title
EmilFattakhov
approved these changes
Jul 3, 2026
- Disable engines-field updates: Renovate kept proposing patch-level floors (e.g. node >=22.23.1, PR #674) that block downstream Yarn Berry consumers without any real compatibility guarantee. Support floors are a human decision. - Remove the automerge rule entirely. It was broken anyway (matchDepTypes with "minor"/"patch", which are update types, so it silently covered all devDependencies updates including majors), and branch protection's required review meant it could never fire. Given npm supply-chain risk, dependency merges stay a deliberate human action; minimumReleaseAge (3/7 days) remains the quarantine. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
jim-counter
force-pushed
the
chore/renovate-config-cleanup
branch
from
July 3, 2026 14:26
7def1de to
cbfe837
Compare
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
2 participants
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.
What
Two changes to
.github/renovate.json:Disable
engines-field updates. Renovate kept proposing patch-level engine floors (chore(deps): update node.js to >=22.23.1 #674 wantednode >=22.23.1), and would re-file after every Node patch release. A patch-level floor blocks downstream consumers — Yarn Berry enforces dependencyenginesstrictly — while guaranteeing nothing, since no code depends on Node patch versions. Engine floors are a support-policy decision for humans. Workflownode-versionupdates (github-actions manager) are unaffected and continue as before (like chore(deps): update node.js to v24 #670).Remove automerge entirely. The existing rule was broken —
matchDepTypes: ["minor", "patch", "devDependencies"]mixes update types into a dep-type matcher, so it silently made all devDependency updates automerge-eligible, majors included. In practice it never fired because branch protection requires an approving review, which Renovate can't provide. Rather than fix the rule, remove it: given the recent npm supply-chain attacks, dependency merges should stay a deliberate human action.minimumReleaseAge(3 days, 7 for majors) remains as the quarantine against compromised releases.🤖 Generated with Claude Code