chore: stop dependabot opening major-version PRs - #15
Merged
Conversation
Grouping only covers minor and patch, so every major arrived as its own PR — 9 on the first run (zod 3->4, vite 7->8, typescript 5->7, @types/node 20->26, and so on). All 9 were closed unmerged. Majors get done deliberately instead. The vitest 1->4 upgrade is the case in point: it needed a verified coverage run, and the obvious-looking brace-expansion override had to be rejected because it broke npm run test:coverage. Security updates are unaffected — Dependabot security PRs bypass ignore. github-actions keeps majors: it is grouped into a single PR, so a major there costs one PR rather than many.
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.
Follow-up to closing the 9 Dependabot PRs on this repo.
The
groupsblock only coversminorandpatch, so every major arrived as its own PR:All closed unmerged. Adding
ignoreforversion-update:semver-majoron all three npm/cargo entries.Security updates still come through
ignoreapplies to version updates only — Dependabot security PRs bypass it entirely. Given this repo carried a critical vitest advisory until #5, that distinction is the whole point: the critical would still have opened a PR under this config.github-actions deliberately keeps majors
Grouped with
patterns: ["*"], so a major costs one PR, not many. Tell me if you'd rather suppress those too.Why majors should be manual here
The vitest 1→4 upgrade in #5 needed a verified coverage run, and the obvious
brace-expansionoverride had to be rejected — it madenpm auditread clean while breakingnpm run test:coverage. No automated bump catches that.Test plan
ignorepresent on npm/, npm/desktop, cargo/desktop/src-tauri; absent on github-actionsignoreserialises to the exact shape Dependabot expects