chore(dependabot): add 7-day cooldown to all update blocks#18
Merged
Conversation
nicololuescher
force-pushed
the
chore/dependabot-cooldown
branch
from
b2dba95 to
21ff81c
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
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.
What
Adds a 7-day cooldown (
cooldown: { default-days: 7 }) to everyupdatesblock independabot.yml.Why
Most malicious package releases (typosquats, hijacked maintainers, malicious post-install) are detected and pulled within 24-72h. A 7-day cooldown keeps us out of that danger window for routine version bumps. Security updates are exempt from cooldown, so CVE fixes still land immediately.
7 days is the cross-tool consensus value (Dependabot / Renovate
minimumReleaseAge/ npmmin-release-age). Part of an org-wide rollout across all repos using Dependabot.