Skip to content

chore(deps): group Dependabot updates into one PR per ecosystem per week - #214

Merged
schenksj merged 2 commits into
mainfrom
feature/dependabot-grouped-updates
Oct 14, 2026
Merged

schenksj merged 2 commits into
mainfrom
feature/dependabot-grouped-updates

Conversation

@rbrenton

@rbrenton rbrenton commented Oct 7, 2026

Copy link
Copy Markdown
Contributor

Why

Dependabot opens one pull request per dependency, and in practice those are closed and rebuilt by hand into a consolidation PR. With CI taking about an hour, individual PRs also force a rebase-and-rerun cascade: every merge sends the others back through CI.

What changes (.github/dependabot.yml only)

  • One grouped version-update PR per ecosystem per week. Each ecosystem gets a catch-all group, so everything that survives the ignore rules arrives together. Previously separate groups are folded into it.
  • Security updates get their own group per ecosystem. They are raised when an advisory is published rather than on the weekly schedule, so they are never held behind the weekly PR.
  • Schedules, PR limits, labels and every ignore rule are unchanged.

Things to know

  • Major, minor and patch updates share the weekly PR. If one bump breaks CI, drop it from the PR with @dependabot ignore <dependency> rather than splitting the group.
  • Dependabot gives any dependency that matches no group its own PR, so the catch-all pattern has to stay.
  • Existing individual Dependabot PRs are not regrouped automatically; close them before the next Monday run.

Verification

The file parses and every key is in GitHub's documented Dependabot options. Dependabot cannot be triggered on demand, so the first Monday run is the real test: expect titles like "Bump the all-maven-updates group with N updates". A PR titled "Bump X from a to b" for a single dependency, or an error on the Dependabot tab under Insights, means the grouping did not take effect.

Open question for this repo

native/Cargo.toml pins the tantivy and quickwit forks by git revision. If the first Cargo PR proposes bumps for those, they should get ignore rules, since the forks are meant to move by hand.

Individual Dependabot PRs get closed and hand-consolidated, and with CI
taking about an hour each PR triggers a rebase-and-rerun cascade. Replace
the narrow test-dependencies and tantivy-ecosystem groups with a catch-all
group per ecosystem (Maven, Cargo, GitHub Actions) so the Monday run opens
at most one version-update PR per ecosystem. Security updates get their own
group per ecosystem so they stay off the weekly PR.
@claude

claude Bot commented Oct 7, 2026 •

Copy link
Copy Markdown

Claude encountered an error —— View job


I'll analyze this and get back to you.

@schenksj schenksj left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

@claude

claude Bot commented Oct 14, 2026 •

Copy link
Copy Markdown

Claude encountered an error —— View job


I'll analyze this and get back to you.

@schenksj
schenksj enabled auto-merge (squash) October 14, 2026 00:44
@schenksj
schenksj merged commit b33cca9 into main Oct 14, 2026
3 of 4 checks passed
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.

2 participants