Repository navigation
chore(deps): group Dependabot updates into one PR per ecosystem per week - #214
Merged
Merged
Conversation
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.
rbrenton
had a problem deploying
to
test-runners
October 7, 2026 14:48 — with
GitHub Actions
Failure
rbrenton
had a problem deploying
to
test-runners
October 7, 2026 14:48 — with
GitHub Actions
Failure
|
Claude encountered an error —— View job I'll analyze this and get back to you. |
|
Claude encountered an error —— View job I'll analyze this and get back to you. |
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
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.
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.ymlonly)ignorerules arrives together. Previously separate groups are folded into it.ignorerule are unchanged.Things to know
@dependabot ignore <dependency>rather than splitting the group.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.tomlpins the tantivy and quickwit forks by git revision. If the first Cargo PR proposes bumps for those, they should getignorerules, since the forks are meant to move by hand.