chore(renovate): add top-level minimumReleaseAge for full coverage#156
Merged
Conversation
Follow-up to the 7-day stability PR: the per-rule windows only gate updates those rules match; anything else had no stability window at all. A top-level value covers every update, with rule-level values (including the security null bypass) still overriding it. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
abubnalitic-nbl
approved these changes
Jun 5, 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
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.
Follow-up to the merged 7-day stability window PR: the window only lived in scoped
packageRules, so updates not matched by those rules had no stability gate. A top-levelminimumReleaseAgecovers every update; rule-level values (including the security bypass) still override it.🤖 Generated with Claude Code