Bump the testing group with 2 updates - #1005
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps the testing group with 2 updates: [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8) and [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest). Updates `@vitest/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) Updates `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/coverage-v8" dependency-version: 5.0.0 dependency-type: direct:development update-type: version-update:semver-major dependency-group: testing - dependency-name: vitest dependency-version: 5.0.0 dependency-type: direct:development update-type: version-update:semver-major dependency-group: testing ... Signed-off-by: dependabot[bot] <support@github.com>
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
There was a problem hiding this comment.
🟡 Changes recommended
The Vitest v5 bump introduces a confirmed peer-dependency incompatibility with @cloudflare/vitest-pool-workers (still peering on Vitest v4), which can break installs and/or test execution.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Pull request overview
This PR updates the repository’s testing toolchain by bumping Vitest and its V8 coverage provider to the new major release (Vitest 5), updating both the top-level dependency declarations and the resolved dependency graph in the lockfile.
Changes:
- Bump
vitestfrom^4.1.11to^5.0.0. - Bump
@vitest/coverage-v8from^4.1.11to^5.0.0. - Refresh
package-lock.jsonto reflect Vitest 5’s new dependency set and engine constraints.
File summaries
| File | Description |
|---|---|
| package.json | Updates devDependency versions for Vitest and @vitest/coverage-v8 to v5. |
| package-lock.json | Updates the lockfile to resolve Vitest v5 and its transitive dependency/engine changes. |
Review details
- Files reviewed: 1/2 changed files
- Comments generated: 1
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| "vite": "^8.2.2", | ||
| "vitest": "^4.1.11", | ||
| "vitest": "^5.0.0", | ||
| "wrangler": "~4.107.1" |
Bumps the testing group with 2 updates: @vitest/coverage-v8 and vitest.
Updates
@vitest/coverage-v8from 4.1.11 to 5.0.0Release notes
Sourced from @vitest/coverage-v8's releases.
... (truncated)
Commits
f441c6fchore: release v5.0.0 (#11130)c4473e4fix(coverage): prevent crash on/@fs/prepended virtual files (#11119)897f51fchore: release v5.0.0-rc.4 (#11107)7db80dcchore: release v5.0.0-rc.3 (#11089)5f6a5e8feat(coverage): switch to@vitest/istanbuljspackages (#11053)c6174a6fix(coverage): v8 to ignore Vite SSR's generated import bindings (#11023)af83d1bchore: release v5.0.0-rc.2 (#10976)a7fa111chore: release v5.0.0-rc.1 (#10920)0553851chore: add Knip checks (#10847)b7be731chore: release v5.0.0-beta.7 (#10825)Updates
vitestfrom 4.1.11 to 5.0.0Release 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 <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions