build(deps-dev): Bump @vitest/coverage-v8 from 3.2.4 to 4.0.6 #145
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Bumps [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8) from 3.2.4 to 4.0.6. - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v4.0.6/packages/coverage-v8) --- updated-dependencies: - dependency-name: "@vitest/coverage-v8" dependency-version: 4.0.6 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
added
dependencies
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the Comment |
Deploying blinklabs-vpn with
|
| Latest commit: |
3ea6661
|
| Status: | 🚫 Build failed. |
|
|
Needs ReviewI recommend reviewing this upgrade before merging because upgrading @vitest/coverage-v8 to version 4.0.6 while keeping vitest at version 3.2.4 creates a major version mismatch that could cause compatibility issues. The upgrade path includes 61 new features and 162 bug fixes, but introduces breaking changes in coverage configuration that may affect how coverage reports are generated. Additionally, the version skew between the test runner (vitest 3.x) and coverage provider (coverage-v8 4.x) could lead to unexpected behavior. To proceed safely, both packages should be upgraded together to matching major versions. What we checked
Dependency UsageThis dependency is a development-only testing tool that generates code coverage reports when developers run the test suite, configured to produce text, JSON, and HTML output formats through the vitest test runner. While not directly imported in application code, it's automatically invoked via the "test:coverage" npm script to help developers track which parts of the React-based VPN frontend are tested. The package supports quality assurance processes by providing visibility into test completeness across the codebase, excluding configuration files and test utilities from coverage metrics.
ChangesThe Vitest coverage package received critical security updates to axios and happy-dom dependencies, while introducing two breaking changes: service worker network mocking now works differently in Chromium browsers, and the test framework removed 18 deprecated APIs including the 'basic' reporter, coverage
View 552 more changes
References (5)[1]: @vitest/coverage-v8 is being upgraded to ^4.0.6, but this creates a major version mismatch with vitest which remains at ^3.2.4 (line 53). These packages should be kept in sync to avoid compatibility issues. Line 40 in 3ea6661 [2]: vitest is at version ^3.2.4 while @vitest/coverage-v8 is being upgraded to ^4.0.6, creating a major version skew that could cause runtime errors or configuration incompatibilities. Line 53 in 3ea6661 [3]: Coverage configuration is defined here. Vitest 4.0 introduces breaking changes to coverage behavior, including removal of coverage.all option and changes to how files are included by default. Current config may need updates. Line 45 in 3ea6661 [4]: Official Vitest 4.0 migration guide documents breaking changes including coverage.all removal and requirement for explicit coverage.include configuration. These changes affect how coverage is calculated. (source link) [5]: Breaking change in browser mode affecting service workers and vi.mock interaction in Chromium. While this project uses jsdom environment, the change indicates significant API modifications in v4.0. (source link) fossabot analyzed this PR using dependency research. |
wolf31o2
requested changes
Nov 4, 2025
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
dependabot
bot
deleted the
dependabot/npm_and_yarn/vitest/coverage-v8-4.0.6
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Rebasing might not happen immediately, so don't worry if this takes some time.
Note: if you make any changes to this PR yourself, they will take precedence over the rebase.
Bumps @vitest/coverage-v8 from 3.2.4 to 4.0.6.
Release notes
Sourced from
@vitest/coverage-v8's releases.... (truncated)
Commits
2e7b2b8chore: release v4.0.6e3b7775fix(coverage): prevent filtering out virtual files before remapping to source...ed9fc71chore: release v4.0.59b75ec5chore: release v4.0.4ca1766fchore: release v4.0.307bc56achore: release v4.0.24a28faachore: release v4.0.1da7ce17chore: release v4.0.03e4b6b7chore: release v4.0.0-beta.1935816fefix(coverage): v8 to ignore Vite's generated cjs import helpers (#8718)Maintainer 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 mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@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)