chore: group dependabot updates and stop major bumps - #145
Merged
Conversation
The first scheduled run on 2026-08-10 opened 41 PRs and 41 branches at once, burying the five open human PRs. Two causes. The config declared 17 update entries, one per standalone crate, because crates/* are not workspace members and each carries its own Cargo.lock — so a single tokio release produced six near-identical PRs, and 23 of the 41 were five shared dependencies replayed per crate. And the wildcard semver-major ignore did not hold for the bun ecosystem, which let through vite 6 -> 8, typescript 5 -> 7, @vitejs/plugin-react 4 -> 6, immer 10 -> 11 and lucide-react 0.468 -> 1.30. Collapse the 16 Cargo entries into one using `directories` with a glob, which `directory` does not support, and add `group-by: dependency-name` so one dependency is one PR spanning every crate that uses it. This also keeps shared pins in lockstep and picks up atlas-git, which the old hand-maintained list had missed. Group the bun and github-actions entries the same way, move all three to monthly, and name the four bundler and state-management packages explicitly in `ignore` so a major cannot arrive unattended regardless of why the wildcard was skipped. Targets main rather than the current version branch because Dependabot only reads this file from the default branch; on 0.2.6 it would have no effect until release.
This was referenced Aug 10, 2026
This was referenced Aug 10, 2026
This was referenced Aug 10, 2026
uzayer
added a commit
that referenced
this pull request
Aug 10, 2026
The wildcard `version-update:semver-major` ignore does not hold for this ecosystem. #145 named vite, @vitejs/plugin-react, typescript and immer explicitly after the 2026-08-10 run let those majors through; the very next run, on the merged config, opened react-resizable-panels 2 -> 4. That is six majors through the bun entry against zero through 38 Cargo PRs sharing the same ignore block, so the wildcard is not being applied here rather than being mis-specified. Naming packages one at a time cannot fix it — the next major is always a package nobody has listed. `open-pull-requests-limit: 0` is the documented way to disable version updates for a single package manager. Security update PRs are exempt from the limit, so vulnerability fixes still arrive; only routine version bumps stop. The group and ignore blocks are kept in place, unused, so restoring the previous behaviour is a one-line change once bun support honours ignore.update-types. This matters more for the frontend than it would elsewhere. Per the `dedupe` note in vite.config.ts, a duplicated @codemirror/* or pdfjs-dist in the production bundle silently breaks editor theming and PDF rendering while lint, typecheck, `bun run build` and `bun run dev` all stay green. The check that would catch it is `bun run build:app` and a real window, which no unattended bot PR can attest to.
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
1 participant
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.
What
Dependabot's first scheduled run (2026-08-10) opened 41 PRs and 41 branches in one go, burying the five open human PRs (#91, #95, #96, #97, #98). This collapses the config from 17 update entries to 3.
Why it happened
Fan-out.
crates/*are standalone packages with their ownCargo.lock, not workspace members, so the config listed each one separately. Dependabot sees 16 unrelated projects that happen to share dependencies. One tokio release became six PRs:23 of the 41 were five dependencies replayed per crate. Ten of the seventeen directories also hit their PR limit exactly, so more were queued behind them.
The major-version ignore didn't hold for
bun. All 36 Cargo PRs were patch/minor as configured, but the JS entry let throughvite6 → 8 (#104),typescript5 → 7 (#122),@vitejs/plugin-react4 → 6 (#113),immer10 → 11 (#109) andlucide-react0.468 → 1.30 (#106). I don't have the Dependabot job logs, so I can't say why the wildcard was skipped for that one ecosystem — the fix doesn't depend on knowing.Changes
directorieswith a glob (directorydoesn't support globbing). Picks upatlas-git, which the hand-maintained list had missed.group-by: dependency-nameso one dependency is one PR spanning every crate that uses it. Also keeps shared pins in lockstep instead of letting crates drift between merges.ignore—vite,@vitejs/plugin-react,typescript,immer— so a major can't arrive unattended regardless of why the wildcard was skipped.lucide-reactis deliberately not pinned: an icon rename fails as a red typecheck, so CI catches it and the update is worth taking.Why those four
They're the ones whose breakage is invisible to CI. Per the
dedupenote invite.config.tsand CLAUDE.md, a duplicated@codemirror/*orpdfjs-distin the production bundle silently breaks editor theming and PDF rendering while lint, typecheck,bun run buildandbun run devall stay green. A bundler major is exactly what perturbs module resolution and chunk splitting. Those needbun run build:appand a real window, which is not something a bot PR can attest to.viteand@vitejs/plugin-reactare additionally coupled — they have to move together, and each PR is green in isolation while the pair may not be.Base branch
Targets
mainrather than0.2.6. Dependabot only readsdependabot.ymlfrom the default branch, so on a version branch this would have no effect until release — and the noise continues until then. Small standalone fix per theCONTRIBUTING.mdcarve-out.Effect
Next run: at most 3 + 5 + 3 PRs, most months far fewer, and no unattended majors.
Verification
dependabot.ymlparses as valid YAML (js-yaml), 3 entries resolve as intended