Skip to content

chore(ci): drop scheduled version updates, keep security updates - #22

Merged
freema merged 1 commit into
mainfrom
chore/dependabot-security-only
Jul 31, 2026
Merged

chore(ci): drop scheduled version updates, keep security updates#22
freema merged 1 commit into
mainfrom
chore/dependabot-security-only

Conversation

@freema

@freema freema commented Jul 31, 2026

Copy link
Copy Markdown
Owner

Reverts the scheduled version updates added in #7. Security coverage is unaffected — it moves to where it belongs.

What changed

  • Removed .github/dependabot.yml — this file only drove scheduled version updates (weekly bumps across Go, npm, actions and Docker).
  • Enabled at the repository level (both were previously off):
    • Dependabot alerts
    • Dependabot security updates

Security updates do not need dependabot.yml. They apply repo-wide to every supported ecosystem and raise a PR only when a dependency has a published advisory.

Why

Weekly bumps across four ecosystems produce a continuous stream of PRs, each fanning out to nine CI jobs, overwhelmingly for routine upgrades.

To be clear about what this is not about: the repository is public and every job runs on standard ubuntu-latest runners, where Actions minutes are free and unlimited. There was no billing concern. This is about review attention — a stream of low-signal PRs makes the one that matters easier to miss.

Trade-off

Dependencies will drift between security fixes. Worth a deliberate refresh periodically rather than a continuous trickle.

🤖 Generated with Claude Code

Weekly version bumps across four ecosystems produce a steady stream of PRs
that each fan out to nine CI jobs, for upgrades that are mostly routine.
Dependabot alerts and security updates are enabled at the repository level
instead, so PRs arrive only when a dependency actually has a published
vulnerability.

Actions minutes are not the reason: the repository is public and runs on
standard runners, where they are free. This is about review attention.

Dependencies will drift between security fixes; refresh them deliberately
rather than continuously.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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