Skip to content

fix: drop unsupported cooldown fields from github-actions ecosystem#38

Merged
viniciusdc merged 1 commit into
mainfrom
fix/dependabot-cooldown-github-actions
May 11, 2026
Merged

fix: drop unsupported cooldown fields from github-actions ecosystem#38
viniciusdc merged 1 commit into
mainfrom
fix/dependabot-cooldown-github-actions

Conversation

@viniciusdc

Copy link
Copy Markdown
Owner

Summary

Follow-up to #36. The cooldown block on the github-actions ecosystem only accepts default-dayssemver-major-days, semver-minor-days, and semver-patch-days are npm-only. The validator rejected the config on both #18 and #22 after their rebases pulled in main.

  • Drops the three unsupported fields from the github-actions block.
  • Settles on default-days: 2 for that ecosystem (Actions are SHA-pinned in this repo anyway, so the soak is mostly belt-and-suspenders).
  • Leaves the npm block untouched — per-semver cooldown there is valid.

Test plan

The github-actions ecosystem only accepts `default-days` in the cooldown
block — semver-{major,minor,patch}-days are npm-only. Settling on a 2-day
default for Actions.
@viniciusdc viniciusdc merged commit b4c77a6 into main May 11, 2026
6 checks passed
@viniciusdc viniciusdc deleted the fix/dependabot-cooldown-github-actions branch May 11, 2026 12:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant