Skip to content

chore(deps-dev): bump vitest from 4.1.11 to 5.0.0 - #5900

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

chore(deps-dev): bump vitest from 4.1.11 to 5.0.0#5900
dependabot[bot] wants to merge 1 commit into
developfrom
dependabot/bun/vitest-5.0.0

Conversation

@dependabot

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

Copy link
Copy Markdown
Contributor

Bumps vitest from 4.1.11 to 5.0.0.

Release notes

Sourced from vitest'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
  • f441c6f chore: release v5.0.0 (#11130)
  • d46a747 fix: treat test.describe as a suite during static collection (#11128)
  • 584cf30 fix: add a warning if inline project has duplicate plugins due to unexpected ...
  • f08ce4b fix: apply queued mocks from doMock() in queue order (fixes #10706) (#11127)
  • 897f51f chore: release v5.0.0-rc.4 (#11107)
  • 1339b06 chore(deps): update all non-major dependencies (#11104)
  • 51e9494 feat!: parse files statically in vitest list by default (#11088)
  • 2122ffd fix: propagate --maxWorkers to projects (#11102)
  • dc10f5f fix(browser): report the action error when a task times out (#11101)
  • d4fe198 feat: promote clearCache out of experimental (#11086)
  • Additional commits viewable in compare view

@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](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) 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/vitest)

---
updated-dependencies:
- dependency-name: vitest
  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-5.0.0 branch from 1c68836 to 525dd03 Compare September 9, 2026 23:42
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