Bump @vitest/coverage-v8 from 3.2.6 to 4.1.8 - #291
Conversation
Bumps [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8) from 3.2.6 to 4.1.8. - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md) - [Commits](https://github.com/vitest-dev/vitest/commits/v4.1.8/packages/coverage-v8) --- updated-dependencies: - dependency-name: "@vitest/coverage-v8" dependency-version: 4.1.8 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
📝 WalkthroughSummary by CodeRabbit
WalkthroughThis PR updates the Estimated code review effort🎯 1 (Trivial) | ⏱️ ~1 minute 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@package.json`:
- Line 52: The package.json currently has a peerDependency mismatch:
`@vitest/coverage-v8` is pinned to ^4.1.8 while vitest remains ^3.2.4. Fix by
making the versions compatible — either bump the vitest devDependency to a 4.x
series (e.g., ^4.1.8 or ^4.x) to match `@vitest/coverage-v8`, or downgrade
`@vitest/coverage-v8` to a 3.x release that is compatible with vitest ^3.2.4;
update the corresponding version string for the "vitest" or
"`@vitest/coverage-v8`" entries in package.json and run npm/yarn install to verify
there are no peerDependency conflicts.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository: lokalise/coderabbit/.coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: ca0e9ceb-e51d-4ff1-9562-1ff3142399f5
📒 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.8", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify compatibility contract directly from npm metadata (read-only).
set -euo pipefail
echo "Current package.json entries:"
rg -n '"`@vitest/coverage-v8`"|"vitest"' package.json
echo
echo "`@vitest/coverage-v8`@4.1.8 peerDependencies:"
npm view `@vitest/coverage-v8`@4.1.8 peerDependencies --json
echo
echo "vitest@3.2.4 version check:"
npm view vitest@3.2.4 version
echo
echo "If peerDependencies require vitest ^4, this PR should either:"
echo " 1) bump vitest to a compatible ^4.x in same PR, or"
echo " 2) keep `@vitest/coverage-v8` on a ^3.x compatible line."Repository: lokalise/node-core
Length of output: 503
Fix Vitest coverage plugin peerDependency mismatch
package.json pins @vitest/coverage-v8 to ^4.1.8, whose peerDependencies require vitest: 4.1.8, but vitest is still ^3.2.4 (lines 52 and 58). This can break install/coverage in CI.
Update either by bumping vitest to a compatible ^4.1.8 (or matching 4.x) or by downgrading @vitest/coverage-v8 to the ^3.x compatible line.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@package.json` at line 52, The package.json currently has a peerDependency
mismatch: `@vitest/coverage-v8` is pinned to ^4.1.8 while vitest remains ^3.2.4.
Fix by making the versions compatible — either bump the vitest devDependency to
a 4.x series (e.g., ^4.1.8 or ^4.x) to match `@vitest/coverage-v8`, or downgrade
`@vitest/coverage-v8` to a 3.x release that is compatible with vitest ^3.2.4;
update the corresponding version string for the "vitest" or
"`@vitest/coverage-v8`" entries in package.json and run npm/yarn install to verify
there are no peerDependency conflicts.
|
Superseded by #295. |
Bumps @vitest/coverage-v8 from 3.2.6 to 4.1.8.
Release notes
Sourced from @vitest/coverage-v8's releases.
... (truncated)
Commits
e61f2ddchore: release v4.1.8e4067b3fix(browser): disable clientcdpAPI whenallowWrite/allowExec: false[ba...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)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)