chore(dependabot): security-first posture β ignore majors, keep grouped patch/minor - #299
Conversation
β¦ed patch/minor Dependabot was emitting risky major bumps (TypeScript 5->7, @types/node 20->26 against a Node 22 runtime, jsdom 28->30, jest-dom 6->7) as ungrouped PRs, while its actual value β security-update PRs β was dormant because repo alerts are off. Add ignore rules for version-update:semver-major on the bun and github-actions ecosystems so routine churn is grouped patch/minor only. Security-update PRs are unaffected (they bypass ignore/group rules) and still land when alerts are on; majors become an opt-in, by-hand decision. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. π βΉοΈ Recent review infoβοΈ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: π Files selected for processing (1)
π WalkthroughWalkthroughDependabot documentation now defines security and routine update behavior. Bun major updates are ignored. GitHub Actions updates run weekly against ChangesDependabot policy
Estimated code review effort: 1 (Trivial) | ~5 minutes Suggested reviewers: π₯ Pre-merge checks | β 4 | β 1β Failed checks (1 warning)
β Passed checks (4 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 |
There was a problem hiding this comment.
Actionable comments posted: 1
π€ Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/dependabot.yml:
- Around line 4-6: Update the explanatory comment near the βDependabot alertsβ
note to require enabling both Dependabot alerts and Dependabot security updates
in repository settings, while preserving the existing description of
security-update PR behavior.
πͺ Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
βΉοΈ Review info
βοΈ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 41dada55-08e6-4a2e-9452-43a5f4eb3ac7
π Files selected for processing (1)
.github/dependabot.yml
β¦quired CodeRabbit: security-update PRs need 'Dependabot security updates' enabled in addition to 'Dependabot alerts' β alerts alone surface the CVE but don't open a PR. Clarify the comment so the requirement is explicit. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
π¦ ClawReviewClaws waving β here's what this change is about. This PR tightens ClawBox's Dependabot posture to security-first by adding At a glance
Good to know
β ClawReview π¦, scuttling off. General info only β see CodeRabbit for the detailed review. Conventions: docs. |
Why
Dependabot is currently emitting risky major version bumps as individual PRs β TypeScript 5β7,
@types/node20β26 (against a Node 22 runtime), jsdom 28β30, jest-dom 6β7 β while its actual value, security-update PRs, is dormant because repo Dependabot alerts are disabled.For an edge-deployed, network-exposed device OS, stability beats currency for routine deps. This shifts Dependabot to a security-first, low-churn posture.
What changed
ignorerules forversion-update:semver-majoron the bun and github-actions ecosystems.ignore/group rules and still land when alerts are enabled. Majors that fix a real CVE still come through as security updates.open-pull-requests-limit: 0(security-only) entry is unchanged.Companion action (admin, not in this PR)
Enable Dependabot alerts in Settings β Code security β that turns on the security-update PRs this config is built around. Without it, the security half stays dormant.
Queue cleanup
The open major-bump PRs (#291, #293, #290, #292, #286, #287, #288) are being closed as superseded by this policy. The grouped patch/minor PR (#289) is kept for a device-build check before merge.
Config file only β no runtime code touched.
Summary by CodeRabbit