chore: exempt lock file maintenance from minimumReleaseAge check#4815
Merged
escapedcat merged 1 commit intoJun 5, 2026
Merged
Conversation
Lock file maintenance updates are package-manager-controlled and have no release timestamp, so the minimumReleaseAge (renovate/stability-days) status check can never pass. These PRs sit pending forever (e.g. #4786, #4775) even though all real CI is green and the check is non-required. Add a packageRule setting minimumReleaseAge: null for the lockFileMaintenance update type, mirroring Renovate's own security:minimumReleaseAgeNpm preset ("Do not require Minimum Release Age for update types that are controlled by the package manager"). The 3-day gate and internalChecksFilter: strict stay in effect for all regular dependency updates. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Review Summary by QodoExempt lock file maintenance from minimumReleaseAge check
WalkthroughsDescription• Exempt lock file maintenance from minimumReleaseAge check • Add packageRule setting minimumReleaseAge to null • Prevent lock maintenance PRs from pending indefinitely • Mirror Renovate's security:minimumReleaseAgeNpm preset behavior Diagramflowchart LR
A["Renovate Config"] -->|packageRule added| B["Lock File Maintenance"]
B -->|minimumReleaseAge: null| C["Skip stability check"]
C -->|Regular updates unaffected| D["3-day gate remains"]
File Changes1. package.json
|
Code Review by Qodo🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)
Great, no issues found!Qodo reviewed your code and found no material issues that require review |
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
1 participant
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.
Lock file maintenance updates are package-manager-controlled and have no release timestamp, so the minimumReleaseAge (renovate/stability-days) status check can never pass. These PRs sit pending forever (e.g. #4786, #4775) even though all real CI is green and the check is non-required.
Add a packageRule setting minimumReleaseAge: null for the lockFileMaintenance update type, mirroring Renovate's own security:minimumReleaseAgeNpm preset ("Do not require Minimum Release Age for update types that are controlled by the package manager"). The 3-day gate and internalChecksFilter: strict stay in effect for all regular dependency updates.