Skip to content

chore(deps): bump @vitest/coverage-v8 from 3.2.6 to 4.1.8#219

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/vitest/coverage-v8-4.1.8
Open

chore(deps): bump @vitest/coverage-v8 from 3.2.6 to 4.1.8#219
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/vitest/coverage-v8-4.1.8

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jun 6, 2026

Copy link
Copy Markdown
Contributor

Bumps @vitest/coverage-v8 from 3.2.6 to 4.1.8.

Release notes

Sourced from @​vitest/coverage-v8's releases.

v4.1.8

   🐞 Bug Fixes

    View changes on GitHub

v4.1.7

   🐞 Bug Fixes

    View changes on GitHub

v4.1.6

   🐞 Bug Fixes

   🏎 Performance

    View changes on GitHub

v4.1.5

   🚀 Experimental Features

   🐞 Bug Fixes

    View changes on GitHub

... (truncated)

Commits

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Jun 6, 2026
@zjshen14

zjshen14 commented Jun 8, 2026

Copy link
Copy Markdown
Owner

Review: chore(deps): bump @vitest/coverage-v8 from 3.2.4 to 4.1.8

This is the companion half of the coordinated vitest 3→4 upgrade. CI is unstable for the same peer-dep reason as #176 and #206: vitest (the runner) is still pinned to ^3.2.4, and vitest 3 and @vitest/coverage-v8 4.x require each other to be at the same major — they can't coexist.

Both halves need to land in the same commit or back-to-back in a coordinated sequence. The standing recommendation from the #206 review still applies: a single combined PR bumping both vitest and @vitest/coverage-v8 to 4.x, handling any vitest 3→4 API breaks, and passing CI green before merge is the cleanest path.

Not merging: CI is red and this PR cannot pass on its own without a matching vitest bump.


Generated by Claude Code

@dependabot dependabot Bot force-pushed the dependabot/npm_and_yarn/vitest/coverage-v8-4.1.8 branch from 4e8ad68 to 53dc917 Compare June 8, 2026 16:19
@zjshen14

zjshen14 commented Jun 9, 2026

Copy link
Copy Markdown
Owner

Rebased to SHA 53dc9173 (main moved forward to ac0daccd), but the diagnosis is unchanged: @vitest/coverage-v8 4.x requires vitest 4.x as a peer dep, while vitest is still on 3.2.x on main. CI fails at startup for the same peer-dep mismatch noted in the prior review.

The coordinated upgrade path remains the cleanest resolution: one PR bumping both vitest and @vitest/coverage-v8 to 4.x, handling any vitest 3→4 API breaks, and passing CI green before merge.

Not merging: CI is red and this PR cannot pass on its own.


Generated by Claude Code

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>
@dependabot dependabot Bot changed the title chore(deps): bump @vitest/coverage-v8 from 3.2.4 to 4.1.8 chore(deps): bump @vitest/coverage-v8 from 3.2.6 to 4.1.8 Jun 9, 2026
@dependabot dependabot Bot force-pushed the dependabot/npm_and_yarn/vitest/coverage-v8-4.1.8 branch from 53dc917 to a43cdc2 Compare June 9, 2026 16:13
@zjshen14

Copy link
Copy Markdown
Owner

Rebased to SHA a43cdc272c (main has moved forward since the last review), but the diagnosis is unchanged.

@vitest/coverage-v8 4.x declares vitest: "4.1.8" as a required peer dep, while vitest is still pinned to ^3.2.4 in package.json on main. CI fails at startup with the same peer-dep mismatch that the previous reviews flagged. This PR cannot pass CI on its own.

The coordinated upgrade path remains the cleanest resolution: one PR bumping both vitest and @vitest/coverage-v8 to 4.x, handling any vitest 3→4 API changes, and passing CI green before merge.

Not merging: CI is red and the change is incomplete without the companion vitest upgrade.


Generated by Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant