Dependabot: a 7-day cooldown before proposing a new action version #1464
No reviewers
Labels
No labels
accessibility
autorelease: pending
autorelease: tagged
bug
dependencies
documentation
duplicate
enhancement
github_actions
good first issue
help wanted
invalid
question
testing wanted
wontfix
No milestone
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Hookshot!1464
Loading…
Reference in a new issue
No description provided.
Delete branch "sec/dependabot-cooldown"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
.github/dependabot.ymlproposed every GitHub Action's newest release once a week, however new it was. A compromised action version (the tj-actions/changed-files pattern) is usually found and pulled within days. Withcooldown: default-days: 7, Dependabot proposes a version only once it is a week old, so a bad release has usually been caught before it can reach the pinned workflows. The weekly schedule, grouping and commit pinning are unchanged.This came from a Syntak Code Security scan of
main(ruledependabot-missing-cooldown). It was the only finding in that scan that needed a change; the triage of the other 38 is in the Discord #dev-stuff channel.Tested
The YAML parses to the expected structure (
updates[0].cooldown.default-days = 7).cooldownis a documented Dependabot option for thegithub-actionsecosystem.🤖 Generated with Claude Code