ci(dependabot): require 7-day cooldown for dependency upgrades#487
Merged
mergify[bot] merged 1 commit intoMay 22, 2026
Conversation
Change-Id: I3178a090b07d4cf135ca3254ed0a1b883ecc478c
Contributor
Merge ProtectionsYour pull request matches the following merge protections and will not be merged until they are valid. 🟢 Required ReviewsWonderful, this rule succeeded.
🟢 Enforce conventional commitWonderful, this rule succeeded.Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/
🟢 🔎 ReviewsWonderful, this rule succeeded.
🟢 📕 PR descriptionWonderful, this rule succeeded.
|
There was a problem hiding this comment.
Pull request overview
This PR aims to reduce Dependabot PR churn by enforcing a 7-day “cooldown” between dependency upgrade PRs for both npm and GitHub Actions updates.
Changes:
- Adds a
cooldown: default-days: 7stanza to the npm Dependabot update config. - Adds the same
cooldownstanza to the GitHub Actions Dependabot update config.
Comments suppressed due to low confidence (1)
.github/dependabot.yml:22
cooldownis not a recognized key in the Dependabot v2 configuration schema, so this will cause the config to be rejected and Dependabot updates to stop. Use a supportedweeklyschedule to approximate a 7-day cooldown and removecooldown.
cooldown:
default-days: 7
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
remyduthu
approved these changes
May 22, 2026
JulianMaurin
approved these changes
May 22, 2026
Contributor
Merge Queue Status
This pull request spent 2 minutes 32 seconds in the queue, including 1 minute 46 seconds running CI. Required conditions to merge
|
34 tasks
mergify
Bot
deleted the
devs/kozlek/ci/dependabot-cooldown/require-7-day-cooldown-dep-upgrades--3178a090
branch
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.
Mitigate supply chain attacks by waiting 7 days before adopting any new dependency release. Most compromised packages (Shai-Hulud, ua-parser-js, eslint-config-prettier, etc.) are detected and yanked within hours-to-days of publication, so a release-age delay catches the overwhelming majority of malicious releases before they hit our lockfiles.
Security updates bypass this delay automatically — Dependabot's
cooldownoption is documented as "only available for version updates, not security updates", so CVE fixes still ship without waiting.Mirrors the equivalent change in the Mergify monorepo (which uses Renovate's
minimumReleaseAge): Mergifyio/mergify#31013.