Skip to content

chore(deps-dev): bump @vitest/coverage-v8 from 4.1.11 to 5.0.0 - #5902

Open
dependabot[bot] wants to merge 1 commit into
developfrom
dependabot/bun/vitest/coverage-v8-5.0.0
Open

dependabot[bot] wants to merge 1 commit into
developfrom
dependabot/bun/vitest/coverage-v8-5.0.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 9, 2026

Copy link
Copy Markdown
Contributor

Bumps @vitest/coverage-v8 from 4.1.11 to 5.0.0.

Release notes

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

v5.0.0

Vitest 5 is officially out! This release focuses on performance and brings a lot of new features while fixing long-standing bugs. See our blog post for the official announcement.

   🚨 Breaking Changes

... (truncated)

Commits

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Sep 9, 2026
@nabramovitz

Copy link
Copy Markdown
Contributor

Blocked by Angular 22, not by a migration cost.

@angular/build@22.1.7 — the latest published, there is no 22.2 or 23 — declares peerDependencies.vitest: "^4.0.8", and @analogjs/vitest-angular@2.7.2 (also latest) declares "^1.3.1 || ^2.0.0 || ^3.0.0 || ^4.0.0". Vitest 5 sits outside both ranges, which is why the frontend test jobs fail across all eight projects here.

The three vitest packages move as one unit — #5900 (vitest), #5902 (@vitest/coverage-v8), #5904 (@vitest/ui). The green CI on the coverage and ui PRs only reflects that nothing in the pipeline exercises them against the runner; merging either on its own would leave a mismatched major.

Leaving this open on purpose rather than closing it, so the bump stays tracked in one place. Worth revisiting once @angular/build and @analogjs/vitest-angular widen their peer ranges.

Bumps [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8) from 4.1.11 to 5.0.0.
- [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/v5.0.0/packages/coverage-v8)

---
updated-dependencies:
- dependency-name: "@vitest/coverage-v8"
  dependency-version: 5.0.0
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/bun/vitest/coverage-v8-5.0.0 branch from 4fa261e to 455e523 Compare September 11, 2026 16:50
@nabramovitz

Copy link
Copy Markdown
Contributor

Status update — 2026-09-12

Re-tested. Full analysis is on #5900; the short version for this PR:

vitest 5 peers @vitest/coverage-v8 at exactly 5.0.0, so this cannot land on its own — it moves with #5900 and the other companion or not at all. The green CI here is not evidence it works: nothing in the pipeline exercises @vitest/coverage-v8 against the runner, so merging this alone would leave a mismatched major and break test:coverage silently.

What actually blocks the set has changed, and it is smaller than previously recorded. The Angular/analog peer ranges are not the blocker — bun does not fail on peer conflicts and @angular/build is not in the test path. The two real issues are a missing @oxc-project/runtime (one package, clears 679/679 failures) and vitest 5 ignoring --project, which is a config migration in vitest.config.ts rather than an upstream incompatibility.

Staying open, pending that work on #5900.

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