Repository navigation
ci: Add 14-day cooldown to Dependabot GitHub Actions updates - #210
Merged
Merged
Conversation
Only propose action versions released at least 14 days ago, matching the org-wide config in igniteui-blazor. Security updates bypass the cooldown. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
rkaraivanov
approved these changes
Oct 13, 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.
Adds a 14-day
cooldownto the existinggithub-actionsentry in.github/dependabot.yml. With it, Dependabot only proposes action versions released at least 14 days ago, so a release that turns out to be broken or compromised has two weeks to be caught and pulled before it lands here. Security updates are not affected by the cooldown and still arrive right away.Nothing else in the file changes. The schedule and any other ecosystems stay as they are.
This is the setup we prefer for all existing repos in the IgniteUI organization, so GitHub Actions stay up to date even in repos we touch once every few years. A repo can choose a different update strategy (AppBuilder does), and that's fine.
References:
Tracking: IgniteUI/devops-experiments#55
🤖 Generated with Claude Code