Repository navigation
ci(dependabot): wait 7 days before proposing a new version - #105
Merged
Merged
Conversation
GitHub applies a 3-day cooldown by default. A week gives a broken or compromised release more time to be yanked before Dependabot proposes it. Security updates are not affected.
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
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.
Summary
Dependabot now waits 7 days after a release before proposing it, for every ecosystem (
cooldown.default-days: 7). GitHub's default cooldown is 3 days; the longer wait gives a broken or compromised release time to be yanked before it reaches a pull request. Security updates are not affected. Only the cooldown blocks are added; schedules, groups, limits, ignores and commit prefixes stay as they are.The pre-commit hooks passed on the changed file; the full
maketarget was not run, CI covers it.Pull request checklist
masterbranchmake checklocally before creating the commit and it has run successfullymake ansible-syntax-checklocally and it has passedConventional Commits with a scope
(
type(scope): subject), and its type matches whether the change ships (feat/fixonly forwhat changes the playbook)
WIPcommits in this PRType of changes