chore: narrow dependabot to github-actions only 🔧#1408
Merged
Conversation
Weekly auto-bumps for npm and docker generated more triage cost than security value: 12+ open PRs after one sweep, several already failing CI on real incompatibilities, attention pulled away from real work. Switch to: - github-actions weekly via this config (rarely breaks, CVE-relevant) - npm + docker bumps done intentionally on chore/deps-YYYY-MM branches by a human, in batches, with local verification - GitHub's native Dependabot security updates (CVE-only, configured in repo Settings) for everything else Net effect: no more weekly npm firehose; security patches still land automatically.
This was referenced May 11, 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
1 participant
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.
Summary
Replaces the broad npm/docker/github-actions dependabot config (#1388) with a github-actions-only setup.
Why
The initial broad config produced 12+ PRs in a single sweep, several already failing CI on real incompatibilities (Apollo, FluentUI, ESLint, TypeScript, Babel groups). For a production multi-tenant SaaS, weekly application-dep auto-bumps are net-negative triage cost. The security value comes from CVE patches, not from chasing minor version churn.
New strategy
chore/deps-YYYY-MMbranchesThis is also superseding #1407 (which added a
nodemajor-bump ignore to the docker ecosystem) - the docker ecosystem is gone entirely, so the ignore rule isn't needed.Test plan