Skip to content

chore(deps): bump @vitest/coverage-v8 from 1.6.0 to 4.0.18 #10

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): bump @vitest/coverage-v8 from 1.6.0 to 4.0.18 #10

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 @@ -64,7 +64,7 @@
"@typescript-eslint/eslint-plugin": "^8.46.1",
"@typescript-eslint/parser": "^8.46.1",
"@types/node": "^25.3.2",
"@vitest/coverage-v8": "1.6.0",
"@vitest/coverage-v8": "4.0.18",
Copy link
Copy Markdown

@sentry sentry Bot Mar 9, 2026

Choose a reason for hiding this comment

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

Bug: The update to @vitest/coverage-v8 to version 4.0.18 without a corresponding update to the vitest package will cause a runtime failure during test execution.
Severity: CRITICAL

Suggested Fix

Update the vitest package to a version compatible with @vitest/coverage-v8@4.0.18, likely a 4.x version. Both dependencies should be on the same major version to ensure compatibility. For example, update vitest to ^4.0.18.

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#L67

Potential issue: The PR updates `@vitest/coverage-v8` to version `4.0.18` while the
`vitest` package remains at `^1.6.0`. These packages are part of the same monorepo and
are tightly coupled, requiring matching major versions. The v4 coverage provider has
internal API incompatibilities with the v1 `vitest` runner. When the `test:coverage`
script is executed, `vitest` will fail to load the coverage provider, causing a runtime
error. This will break the CI/CD pipeline, specifically the `verify:release` script, and
block future releases.

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

"eslint": "^9.37.0",
"globals": "^16.4.0",
"ts-node": "^10.9.2",
Expand Down
Loading