chore(deps): consolidate dependabot into one grouped PR, minor/patch only - #47
Conversation
…only Routine version updates are limited to minor and patch; semver-major bumps are ignored. The version-update: prefix scopes that ignore to version updates only, so a security advisory that can only be fixed by a major bump still opens a PR. Updates are grouped so they arrive as a single PR rather than one per dependency. Security advisories are grouped separately, per ecosystem. Mirrors the configuration proven on alaska-rcv, where it took 15 open Dependabot PRs down to 1. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FpuRSSAYEkdSSgnaFaoBKK
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughDependabot now combines cargo, pip, Docker, and GitHub Actions updates into one weekly group. Each ecosystem ignores semver-major version updates and has a separate security-update group. ChangesDependabot update policy
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Change: Other Merge Risk: ⚪ Minimal · up to The configuration preserves major-version security updates while limiting routine updates. No actionable merge risk remains. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Part of an org-wide Dependabot consolidation. This repo currently has 5 open Dependabot PRs.
What changes
1. Routine updates are minor/patch only.
The
version-update:prefix scopes this to version updates. Security updates are filtered separately, so an advisory whose only fix is a major bump still opens a PR. Dropping theupdate-types:key would turn this into a blanket ignore that silences security updates too — there's a comment in the file saying so.2. One PR instead of one per dependency.
multi-ecosystem-groupsmerges cargo + pip + docker + github-actions into a single weekly PR. This is the exact shape proven on alaska-rcv.3. Security advisories grouped separately via
*-securitygroups withapplies-to: security-updates, so they arrive as one PR per ecosystem rather than one per advisory.Proven on alaska-rcv
This mirrors the config now running on alaska-rcv, which took 15 open Dependabot PRs down to 1 and correctly suppressed major bumps (
@mui/material7.1.0→9.3.1 became 7.1.0→7.3.11;node20.11.1→26.8 became 20.11.1→20.20.2).Two things that pilot taught us, both encoded here:
open-pull-requests-limitmust not appear on an update entry belonging to a multi-ecosystem group — Dependabot rejects the entire file, and the published JSON schema does not catch it. It's omitted on multi-ecosystem repos entirely.applies-tokey, so it covers version updates only. Hence the separate*-securitygroups.Note on merging
Nothing takes effect until this is merged — Dependabot only reads config from the default branch. Stale PRs will be closed separately, after this is confirmed parsing, and only ones with no matching security alert. This repo has 0 open security alerts, so nothing here is a security PR.
🤖 Generated with Claude Code
https://claude.ai/code/session_01FpuRSSAYEkdSSgnaFaoBKK
Summary by CodeRabbit