chore(renovate): apply a 3-day minimumReleaseAge cooldown to updates - #393
Merged
Merged
Conversation
…391) Renovate now waits 3 days after a release is published before opening or automerging an update PR for it, giving the ecosystem time to detect and unpublish compromised versions. Security remediation PRs keep Renovate's default bypass of the cooldown, documented explicitly in the config. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
Closes #391.
What
minimumReleaseAgeof 3 days inrenovate.json, so Renovate waits 3 days after a version is published before opening (or automerging) an update PR for it. The option is inherited by all package rules — including the automerged minor/patch rule — and by lock file maintenance.vulnerabilityAlerts.minimumReleaseAgeis nownullexplicitly, with an in-configdescriptiondocumenting the decision — a known vulnerability in the currently used version outweighs the supply-chain wait for the fixed version.Why
Minor/patch updates automerge weekly with no human in the loop, so a compromised release could land in
mainbefore the ecosystem catches it. A 3-day cooldown gives time for malicious versions to be detected and unpublished. This is independent of the npm-CLI cooldown (#390): Renovate resolves updates on its own runners, so its own config is the lever for the automated path.Verification
renovate-config-validator renovate.jsonpasses (including--strict)