Bump @vitest/coverage-v8 from 3.2.4 to 4.1.1#267
Bump @vitest/coverage-v8 from 3.2.4 to 4.1.1#267dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
Bumps [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8) from 3.2.4 to 4.1.1. - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v4.1.1/packages/coverage-v8) --- updated-dependencies: - dependency-name: "@vitest/coverage-v8" dependency-version: 4.1.1 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
requested review from
a team,
CarlosGamero,
drdaemos and
kibertoad
as code owners
📝 WalkthroughSummary by CodeRabbit
WalkthroughThe Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes 🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@package.json`:
- Line 52: package.json currently lists `@vitest/coverage-v8`@4.1.1 which requires
vitest@4.1.1 while vitest is still pinned to 3.2.4; update the dependency pair
to be compatible by either bumping "vitest" to "^4.1.1" to match
"@vitest/coverage-v8" or downgrading "@vitest/coverage-v8" to a 3.x release
(e.g., "^3.2.4"); edit the dependencies/devDependencies entries for "vitest" and
"@vitest/coverage-v8" in package.json so their major versions align, then run
npm/yarn install and verify tests run.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository: lokalise/coderabbit/.coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 68aa6788-be38-4e0a-a6e9-be71d048be4d
📒 Files selected for processing (1)
package.json
| "@types/node": "^25.0.2", | ||
| "@types/tmp": "^0.2.6", | ||
| "@vitest/coverage-v8": "^3.2.4", | ||
| "@vitest/coverage-v8": "^4.1.1", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Description: Check peerDependencies of `@vitest/coverage-v8`@4.1.1 to verify vitest version requirements
# Fetch package metadata and extract peerDependencies
curl -s https://registry.npmjs.org/@vitest/coverage-v8/4.1.1 | jq '{
version: .version,
peerDependencies: .peerDependencies,
engines: .engines
}'Repository: lokalise/node-core
Length of output: 188
🌐 Web query:
vitest v4 coverage-v8 compatibility requirements with vitest v3
💡 Result:
-
@vitest/coverage-v8is version-locked to Vitest (exact match), not just “compatible by major”.@vitest/coverage-v8@3.0.8declares peerDependencies:"vitest": "3.0.8"(and optional@vitest/browser: "3.0.8"). [1]@vitest/coverage-v8@4.1.0declares peerDependencies:"vitest": "4.1.0"(and optional@vitest/browser: "4.1.0"). [2]
Implication: You generally can’t use a v4coverage-v8with Vitest v3 (or vice‑versa) without peer-dep conflicts; install the same version as yourvitest.
-
If you upgrade from Vitest v3 → v4, expect coverage output changes (even with the same
v8provider). Vitest v4’s V8 coverage remapping logic changed and can affect reported results. [3] -
Extra requirement when moving to Vitest v4: Vitest
4.0.0requires Node^20 || ^22 || >=24. [4]
Sources:
[1] @vitest/coverage-v8@3.0.8 package.json (peerDependencies) [1]
[2] @vitest/coverage-v8@4.1.0 package.json (peerDependencies) [2]
[3] Vitest Migration Guide (v4 V8 coverage changes) [3]
[4] vitest@4.0.0 package.json (engines.node) [4]
Resolve version incompatibility: @vitest/coverage-v8@4.1.1 requires vitest@4.1.1.
The coverage plugin @vitest/coverage-v8@4.1.1 (line 52) declares an exact peer dependency on vitest@4.1.1, but the main package (line 58) remains at vitest@3.2.4. This version mismatch will cause peer dependency conflicts and break test coverage functionality.
Upgrade vitest to ^4.1.1 to match the coverage plugin, or revert the coverage plugin to ^3.2.4.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@package.json` at line 52, package.json currently lists
`@vitest/coverage-v8`@4.1.1 which requires vitest@4.1.1 while vitest is still
pinned to 3.2.4; update the dependency pair to be compatible by either bumping
"vitest" to "^4.1.1" to match "@vitest/coverage-v8" or downgrading
"@vitest/coverage-v8" to a 3.x release (e.g., "^3.2.4"); edit the
dependencies/devDependencies entries for "vitest" and "@vitest/coverage-v8" in
package.json so their major versions align, then run npm/yarn install and verify
tests run.
Bumps @vitest/coverage-v8 from 3.2.4 to 4.1.1.
Release notes
Sourced from
@vitest/coverage-v8's releases.... (truncated)
Commits
1f2d318chore: release v4.1.1aaf9f18fix(coverage): simplify provider types (#9931)4150b91chore: release v4.1.00c2c013chore: release v4.1.0-beta.6689a22afix(browser): types ofgetCDPSessionandcdp()(#9716)94eb73bchore(deps): update eslint packages (#9615)8c96bb0refator: update links to npmx (#9783)aaf7758chore: standardize packages README (#9776)57cbe39chore(deps): updateast-v8-to-istanbulto v1 (#9755)79672d7chore: release v4.1.0-beta.5Maintainer changes
This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~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)