Skip to content

chore(deps-dev): bump @vitest/coverage-v8 from 2.1.9 to 4.0.18 #4

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
dependabot wants to merge 1 commit into from
Closed

chore(deps-dev): bump @vitest/coverage-v8 from 2.1.9 to 4.0.18 #4

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,7 +59,7 @@
"devDependencies": {
"@types/node": "^22.10.0",
"@types/ws": "^8.18.1",
"@vitest/coverage-v8": "^2.1.8",
"@vitest/coverage-v8": "^4.0.18",
Copy link
Copy Markdown

@sentry sentry bot Mar 7, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: The PR updates @vitest/coverage-v8 to a new major version (v4) but leaves vitest at v2. These packages must share the same major version to be compatible.
Severity: CRITICAL

Suggested Fix

To resolve the incompatibility, update the vitest package in package.json to a version compatible with @vitest/coverage-v8 v4, such as ^4.0.18. Both packages should share the same major version. After updating package.json, run bun install to update the bun.lock file accordingly.

Prompt for AI Agent 
Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: package.json#L62

Potential issue: The pull request upgrades `@vitest/coverage-v8` to version `^4.0.18`
while `vitest` remains at `^2.1.8`. Vitest and its related packages, like
`@vitest/coverage-v8`, are tightly coupled and require matching major versions for
compatibility. Attempting to run tests with coverage via `vitest run --coverage` will
cause a failure. The v2 `vitest` runner will be unable to initialize the v4 coverage
plugin due to breaking API changes between the major versions, which will break the
CI/CD pipeline's `coverage` job.

Did we get this right? 👍 / 👎 to inform future reviews.

"eslint": "^9.17.0",
"tsx": "^4.19.2",
"typescript": "^5.7.2",
Expand Down
Loading