chore: added 7 day cooldown to dependabot#206
Merged
Conversation
✅ Deploy Preview for pepr-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
samayer12
approved these changes
Feb 12, 2026
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
2 participants
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.
Added
cooldown: default-days: 7to all dependabot configurations. This will delay dependabot from opening a PR for dependency updates until they have matured 7 days. Most security patches will be released within days of a vulnerability being discovered on a new release. A 7 day cooldown will allow those patches to be applied before implementing.Security patches are not affected by the cooldown. Dependabot will continue to open PRs immediately (unchanged workflow) for security patches.
Grouped dependencies PRs will open once all dependencies have individually cleared their cooldown period. This is expected behavior and may add a few extra days of delay for some updates, but keeps PR volume low. If a specific dependency frequently holds up a group, it can be pulled out into its own entry.