Bump @vitest/coverage-v8 from 1.6.1 to 4.1.9#89
Conversation
Bumps [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8) from 1.6.1 to 4.1.9. - [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.9/packages/coverage-v8) --- updated-dependencies: - dependency-name: "@vitest/coverage-v8" dependency-version: 4.1.9 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
major
dependabot
Bot
added
major
📝 WalkthroughSummary by CodeRabbit
WalkthroughThe Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes 🚥 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 |
![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 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 48: Update the vitest dependency version to match the `@vitest/coverage-v8`
package version that was bumped to ^4.1.9. Change the vitest entry in
package.json from v1.5.3 to ^4.1.9 to resolve the peer dependency violation
between vitest and `@vitest/coverage-v8` and ensure compatibility.
🪄 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: 8920d847-05bd-41f9-8839-d3234f9c1936
📒 Files selected for processing (1)
package.json
| "@typescript-eslint/eslint-plugin": "^7.8.0", | ||
| "@typescript-eslint/parser": "^7.8.0", | ||
| "@vitest/coverage-v8": "^1.5.3", | ||
| "@vitest/coverage-v8": "^4.1.9", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "== package.json: vitest-related deps =="
python - <<'PY'
import json
from pathlib import Path
p = Path("package.json")
data = json.loads(p.read_text())
for section in ("dependencies", "devDependencies", "peerDependencies", "optionalDependencies"):
deps = data.get(section, {})
selected = {k:v for k,v in deps.items() if k == "vitest" or k.startswith("`@vitest/`")}
if selected:
print(f"[{section}]")
for k,v in sorted(selected.items()):
print(f" {k}: {v}")
PY
echo
echo "== lockfile hits for vitest-related packages (if lockfiles exist) =="
fd -HI 'pnpm-lock.yaml|package-lock.json|yarn.lock' . | while read -r lock; do
echo "--- $lock ---"
rg -n -C2 '`@vitest/coverage-v8`|\"vitest\"|`@vitest/`' "$lock" || true
doneRepository: lokalise/zod-extras
Length of output: 238
🌐 Web query:
What are the peer dependency requirements for @vitest/coverage-v8 4.1.9, and which Vitest major versions are supported?
💡 Result:
The @vitest/coverage-v8 package version 4.1.9 has the following peer dependency requirements [1]: 1. vitest: 4.1.9 [1] 2. @vitest/browser: 4.1.9 (optional) [1] Regarding supported Vitest major versions, @vitest/coverage-v8 4.1.9 is designed for compatibility with Vitest 4.x [1][2]. Vitest packages typically maintain strict version parity with their corresponding peer dependencies [1][3]. As of June 2026, Vitest 4.x is the current major version series [1][2].
Citations:
- 1: https://npmx.dev/package/@vitest/coverage-v8
- 2: https://www.npmjs.com/package/@vitest/coverage-v8
- 3: https://registry.npmjs.org/@vitest/coverage-v8
Fix vitest version to match @vitest/coverage-v8 major version.
The PR bumps @vitest/coverage-v8 to v4.1.9 (which requires vitest: 4.1.9), but vitest remains at v1.5.3. This creates a peer dependency violation that will break coverage and potentially runtime behavior. Upgrade vitest to ^4.1.9 to align with the coverage plugin.
🤖 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 48, Update the vitest dependency version to match the
`@vitest/coverage-v8` package version that was bumped to ^4.1.9. Change the vitest
entry in package.json from v1.5.3 to ^4.1.9 to resolve the peer dependency
violation between vitest and `@vitest/coverage-v8` and ensure compatibility.
|
Superseded by #95. |
dependabot
Bot
deleted the
dependabot/npm_and_yarn/vitest/coverage-v8-4.1.9
branch
Bumps @vitest/coverage-v8 from 1.6.1 to 4.1.9.
Release notes
Sourced from @vitest/coverage-v8's releases.
... (truncated)
Commits
a7a61e7chore: release v4.1.9 (#10598)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.1Maintainer 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)