Repository navigation
chore(deps): bump vitest from 4.1.10 to 5.0.0 - #634
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 4.1.10 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:production ... Signed-off-by: dependabot[bot] <support@github.com>
|
Standing release PR: #614 · v0.42.0 queued (4 packages) · open 42d 19h 29m · ✅ ready to merge Release Preview — v0.41.2 → v0.41.3
These changes will be added to the release PR (#614) when merged: Changelogmonorepo 0.41.2 → 0.41.3
After merge — predicted release
Updated automatically by ReleaseKit |
| tsx: ^4.23.1 | ||
| typescript: ^5.9.3 | ||
| vitest: ^4.1.10 | ||
| vitest: ^5.0.0 |
There was a problem hiding this comment.
Coverage Versions No Longer Match
Upgrading Vitest alone leaves every coverage-enabled test run on an unsupported mixed-major pair. The catalog still installs @vitest/coverage-v8@4.1.10, which requires Vitest 4.1.10, while Vitest 5.0.0 requires coverage-v8 5.0.0. The shared configuration enables the v8 provider, so coverage runs now emit a version-mismatch warning and use an unsupported provider contract. Please upgrade the coverage provider in lockstep with Vitest.
| tsx: ^4.23.1 | ||
| typescript: ^5.9.3 | ||
| vitest: ^4.1.10 | ||
| vitest: ^5.0.0 |
There was a problem hiding this comment.
Vitest 5 requires Node ^22.12.0 || ^24.0.0 || >=26.0.0, but this repository still declares and documents Node 22 generally as supported. Developers using Node 22.0–22.11 therefore meet the repository's stated requirement but cannot run the upgraded test toolchain. Please raise the Node 22 minimum to 22.12 or retain a compatible Vitest version.
|
Superseded by #641. |
Bumps vitest from 4.1.10 to 5.0.0.
Release notes
Sourced from vitest's releases.
... (truncated)
Commits
f441c6fchore: release v5.0.0 (#11130)d46a747fix: treat test.describe as a suite during static collection (#11128)584cf30fix: add a warning if inline project has duplicate plugins due to unexpected ...f08ce4bfix: apply queued mocks from doMock() in queue order (fixes #10706) (#11127)897f51fchore: release v5.0.0-rc.4 (#11107)1339b06chore(deps): update all non-major dependencies (#11104)51e9494feat!: parse files statically in vitest list by default (#11088)2122ffdfix: propagate --maxWorkers to projects (#11102)dc10f5ffix(browser): report the action error when a task times out (#11101)d4fe198feat: promote clearCache out of experimental (#11086)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 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)You can disable automated security fix PRs for this repo from the Security Alerts page.
This PR is not yet safe to merge because it creates an unsupported Vitest/coverage-provider pairing and drops part of the repository's declared Node 22 support.
Findings
Summary
Reviews (1) · Last reviewed commit: "chore(deps): bump vitest from 4.1.10 to ..."