SECENG-347: Add 7-day Dependabot cooldown#8
Merged
Conversation
PR SummaryLow Risk Overview Excludes internal dependencies ( Reviewed by Cursor Bugbot for commit 6707208. Bugbot is set up for automated code reviews on this repo. Configure here. |
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.
JIRA
SECENG-347
What
Adds a 7-day cooldown to all Dependabot updaters, excluding internal packages.
Why
Supply chain attacks typically have exploitation windows of hours to days. A 7-day cooldown closes that window with zero operational cost: version updates are delayed, security updates still come through immediately.
Why cooldowns matter • GitHub cooldown docs
Created by Sourcegraph batch change
tomekchime/batch-dependabot-cooldown-config.