chore: enforce 14-day release age before Dependabot updates - #94
Conversation
Co-authored-by: marcelocra <2532492+marcelocra@users.noreply.github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Co-authored-by: marcelocra <2532492+marcelocra@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
This PR updates the repository’s Dependabot configuration to delay non-security dependency update PRs until a dependency release is at least 14 days old, reducing churn from very recent releases.
Changes:
- Added
cooldown: default-days: 14to each existing Dependabotupdatesentry (npm root, npm/www, GitHub Actions, devcontainers, docker).
Greptile SummaryAdds a 14-day Dependabot release-age cooldown to every configured update ecosystem while preserving the existing schedules, groups, labels, and pull-request limits.
Confidence Score: 5/5The PR appears safe to merge, with no concrete blocking or independently actionable non-blocking issues identified. The configuration consistently adds the intended cooldown under each existing Dependabot update entry, and the available repository evidence reveals no reachable configuration or behavioral failure. Important Files Changed
Reviews (1): Last reviewed commit: "fix: use schema-compatible dependabot co..." | Re-trigger Greptile |
Dependabot was configured with weekly/monthly schedules but no minimum release age gate. This PR adds a global cooldown so update PRs are created only after releases are at least two weeks old.
What changed
.github/dependabot.yml:default-days: 14Resulting behavior