Bump vitest from 4.1.11 to 5.0.0 - #178
dependabot[bot] wants to merge 1 commit into
Conversation
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
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>
0ecebdf to
22e7d91
Compare
Dependabot split this into two separate PRs (#177, #178), but bumping either package alone breaks test:coverage with "coverageFilesDirectory is required" since vitest 5's rewritten coverage provider requires both packages to move in lockstep. Also pins vite as an explicit devDependency: vitest 5 requires vite as a non-optional peer, but legacy-peer-deps=true in .npmrc means npm never auto-installs peer deps, so it was silently dropped from the lockfile when only one of the two packages was bumped. Claude-Session: https://claude.ai/code/session_01PJyro83oZ4SGWgG8Xa7XtP Co-authored-by: Claude <noreply@anthropic.com>
|
Superseded by #179, which bumps Generated by Claude Code |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
Dependabot split the vitest 5.0.0 major bump into two separate PRs (#177, #178) because the existing npm-minor-and-patch group only covers minor/patch updates. Bumping either package alone breaks test:coverage, since vitest's coverage provider requires both on the same major version (fixed together in #179). Add a dedicated vitest group (patterns: vitest, @vitest/*) covering all update types, so future bumps of these packages always land in one PR — same fix already applied to codeql-action after a similar incident. Claude-Session: https://claude.ai/code/session_01PJyro83oZ4SGWgG8Xa7XtP Co-authored-by: Claude <noreply@anthropic.com>
1 participant
Bumps vitest from 4.1.11 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)