chore(deps): bump @vitest/coverage-v8 from 2.1.9 to 4.1.7#42
chore(deps): bump @vitest/coverage-v8 from 2.1.9 to 4.1.7#42dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8) from 2.1.9 to 4.1.7. - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v4.1.7/packages/coverage-v8) --- updated-dependencies: - dependency-name: "@vitest/coverage-v8" dependency-version: 4.1.7 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
github-actions
Bot
added
size/XS
Dependency Changes DetectedThis PR modifies dependency files. Please review whether these changes are intentional. Changed files:
Maintainer checklist:
|
lml2468
left a comment
lml2468
left a comment
There was a problem hiding this comment.
🟡 [COMMENT — self-review] Needs coordination before merge.
@vitest/coverage-v8 2.1.9 → 4.1.7:
✅ Correct direction — v4.1.7 requires vitest: 4.1.7 as peer dependency.
🟡 Peer dependency chain: @vitest/coverage-v8@4.1.7 requires vitest@4.1.7 exactly. The repo is currently on vitest@2.1.9. This PR alone will produce an unmet peer dependency warning/error at runtime.
Required merge order:
- Upgrade
vitestto 4.1.7 (not yet in any open PR) - Upgrade
viteto 8.x (PR #41) — vitest 4 supports vite ^6||^7||^8 - Merge #42 together with the above
🔵 Also note: vitest 4 + coverage-v8 4 requires Node ≥ 20 (already met — CI runs Node 18 and 20; consider dropping Node 18 if it becomes a constraint).
Do not merge standalone. Part of the same coordinated batch as PR #41.
Jerry-Xin
left a comment
Jerry-Xin
left a comment
There was a problem hiding this comment.
This PR is in scope, but it breaks clean installs by upgrading only the Vitest coverage provider to v4 while leaving the test runner on v2.
🔴 Blocking
🔴 Critical — @vitest/coverage-v8@4.1.7 requires vitest@4.1.7, but the project still depends on vitest@^2.1.9. This makes npm ci fail with ERESOLVE could not resolve, so fresh installs and CI will be blocked before tests can run. See package.json and package.json. The lockfile also records the incompatible peer requirement at package-lock.json while keeping vitest at 2.1.9 at package-lock.json.
💬 Non-blocking
None.
✅ Highlights
The PR only touches dev dependency metadata and is relevant to the repository’s existing test:coverage workflow.
Verification: npm ci fails with a peer dependency conflict between @vitest/coverage-v8@4.1.7 and vitest@2.1.9.
lml2468
left a comment
lml2468
left a comment
There was a problem hiding this comment.
[CHANGES_REQUESTED] Independent cross-review. Same pattern as PR #44.
🔴 Blocking: CI red — peer dependency mismatch
While resolving: @vitest/coverage-v8@4.1.7
Found: vitest@2.1.9
Could not resolve dependency:
peer vitest@"4.1.7" from @vitest/coverage-v8@4.1.7
@vitest/coverage-v8 bumped from 2.x to 4.x, but vitest itself is still at ^2.1.9. Coverage-v8 has a strict peer dependency on the exact matching vitest version (peer vitest@"4.1.7").
Required fix: Either:
- Bump
vitestto 4.x alongside@vitest/coverage-v8, OR - Close and configure Dependabot grouping:
groups: vitest: patterns: - "vitest" - "@vitest/*"
Same Dependabot partial-group problem as PR #44 (react). These packages must move together.
2 participants
Bumps @vitest/coverage-v8 from 2.1.9 to 4.1.7.
Release notes
Sourced from @vitest/coverage-v8's releases.
... (truncated)
Commits
a09d472chore: release v4.1.7a8fd24cchore: release v4.1.6e399846chore: release v4.1.5ac04bacchore: release v4.1.42dc0d62chore: release v4.1.3fc6f482chore: release v4.1.21f2d318chore: release v4.1.1aaf9f18fix(coverage): simplify provider types (#9931)4150b91chore: release v4.1.00c2c013chore: release v4.1.0-beta.6Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for
@vitest/coverage-v8since your current version.Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)