Skip to content

chore(deps): consolidate dependabot into one grouped PR, minor/patch only - #16

Merged
3uzbcqje merged 1 commit into
mainfrom
chore/dependabot-consolidate
Sep 14, 2026
Merged

3uzbcqje merged 1 commit into
mainfrom
chore/dependabot-consolidate

Conversation

@3uzbcqje

Copy link
Copy Markdown
Contributor

Part of an org-wide Dependabot consolidation. This repo currently has 6 open Dependabot PRs.

What changes

1. Routine updates are minor/patch onlyignore drops version-update:semver-major. That prefix scopes the ignore to version updates, so a security advisory whose only fix is a major bump still opens a PR. Removing the update-types: key would make it 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. One ecosystem (npm), so a plain patterns: ["*"] group is used; open-pull-requests-limit: 3 stays on the update entry, which is valid there.

3. Security advisories grouped separately via *-security groups with applies-to: security-updates — one PR per ecosystem rather than one per advisory.

Already proven in this org

Running on alaska-rcv (15 PRs → 1), star-view (7 → 1), star-core (5 → 1), starpy and discord-bot.

On star-view, Dependabot took the majors down to the highest in-range version rather than skipping them: react 16.12.0→19.2.8 became 16.12.0→16.14.0, typescript 3.8.3→7.0.2 became 3.8.3→3.9.10.

Two rules learned the hard way, both encoded in the config:

  • open-pull-requests-limit must not appear on an update entry belonging to a multi-ecosystem group — Dependabot rejects the whole file, and the published JSON schema does not catch it.
  • A multi-ecosystem group has no applies-to key, so it covers version updates only. Hence the separate *-security groups.

What happens to the existing PRs

Mostly nothing — Dependabot cleans up after itself. Once this merges, it supersedes its own stale PRs and folds them into the grouped PR automatically. On star-view it closed 7 and replaced them with 1, unprompted.

The exception is PRs whose package has no in-range update left (an orphaned actions/checkout 4→7, say). Those linger and need closing by hand.

This repo has 22 open security alerts. Nothing here will be closed without first cross-referencing every PR against those alerts — see below.

🤖 Generated with Claude Code

https://claude.ai/code/session_01FpuRSSAYEkdSSgnaFaoBKK

…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
@coderabbitai

coderabbitai Bot commented Sep 14, 2026

Copy link
Copy Markdown

Important

  • 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 8a9d9bcd-0263-49ca-8093-5056e5ea205e


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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@3uzbcqje
3uzbcqje merged commit 110d05b into main Sep 14, 2026
2 of 3 checks passed
@3uzbcqje
3uzbcqje deleted the chore/dependabot-consolidate branch September 14, 2026 00:12
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