Repository navigation
Group vitest and @vitest/coverage-v8 dependabot updates - #180
Merged
Merged
Conversation
Dependabot split the vitest 5.0.0 major bump into two separate PRs (#177, #178) because the existing npm-minor-and-patch group only covers minor/patch updates. Bumping either package alone breaks test:coverage, since vitest's coverage provider requires both on the same major version (fixed together in #179). Add a dedicated vitest group (patterns: vitest, @vitest/*) covering all update types, so future bumps of these packages always land in one PR — same fix already applied to codeql-action after a similar incident. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PJyro83oZ4SGWgG8Xa7XtP
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
2 participants
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.
Review
CONTRIBUTING.mdfor the branch workflow,required local checks, and when docs or changelog updates are expected.
Summary
npm-minor-and-patchgroup only covers minor/patch updates — major bumps get their own PR per package.vitestor@vitest/coverage-v8alone breakstest:coverage(fixed together in Bump vitest and @vitest/coverage-v8 to 5.0.0 together #179), so these two packages need to always move in lockstep.vitestgroup (patterns: vitest, @vitest/*) with noupdate-typesrestriction, so it covers major/minor/patch alike — mirrors the existingcodeql-actiongroup added for the same reason (github/codeql-action init/analyze/upload-sarif have to move together too).Verification
npm run validate— not applicable, config-only changeNotes
🤖 Generated with Claude Code
https://claude.ai/code/session_01PJyro83oZ4SGWgG8Xa7XtP
Generated by Claude Code