Bump vitest from 4.1.8 to 5.0.0 - #346
Open
dependabot[bot] wants to merge 1 commit into
Open
Conversation
dependabot
Bot
added
the
dependencies
Contributor
|
@dependabot merge |
Contributor
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.OpenSSF ScorecardScorecard details
Scanned Files
|
Contributor
Author
|
Dependabot can't parse your pnpm-lock.yaml. Because of this, Dependabot cannot update this pull request. |
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/vitest-4.1.10
branch
from
August 18, 2026 19:56
09a22a2 to
0071282
Compare
Contributor
|
@dependabot merge |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
|
|
||
| xlsx@https://cdn.sheetjs.com/xlsx-0.20.3/xlsx-0.20.3.tgz: | ||
| resolution: {integrity: sha512-oLDq3jw7AcLqKWH2AhCpVTZl8mf6X2YReP+Neh0SJUzV/BdZYjth94tG5toiMB1PPrYtxOCfaoUCkvtuH+3AJA==, tarball: https://cdn.sheetjs.com/xlsx-0.20.3/xlsx-0.20.3.tgz} | ||
| resolution: {tarball: https://cdn.sheetjs.com/xlsx-0.20.3/xlsx-0.20.3.tgz} |
There was a problem hiding this comment.
Lockfile drops xlsx integrity
Medium Severity
Updating vitest rewrote the lockfile and removed the integrity hash from the remote xlsx tarball resolution. With pnpm@10.33.2, installs can proceed without verifying that CDN package. On newer pnpm, --frozen-lockfile installs may fail with ERR_PNPM_MISSING_TARBALL_INTEGRITY.
Reviewed by Cursor Bugbot for commit 0071282. Configure here.
Contributor
Author
|
Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting |
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 4.1.8 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: 4.1.10 dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
changed the title
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/vitest-4.1.10
branch
from
September 6, 2026 19:29
0071282 to
e7d004b
Compare
Contributor
|
@dependabot merge |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 2 potential issues.
There are 3 total unresolved issues (including 1 from previous review).
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit e7d004b. Configure here.
| "devDependencies": { | ||
| "turbo": "^2.9.14", | ||
| "vitest": "^4.1.8" | ||
| "vitest": "^5.0.0" |
There was a problem hiding this comment.
Vitest 5 needs Node 22
High Severity
vitest 5 requires Node ^22.12.0, but the repo still targets Node 20: engines is >=20.16.0 <24, .nvmrc pins 20, and the test workflow runs node-version: "20". pnpm test on the documented and CI Node version is unsupported and will fail.
Additional Locations (2)
Reviewed by Cursor Bugbot for commit e7d004b. Configure here.
| "devDependencies": { | ||
| "turbo": "^2.9.14", | ||
| "vitest": "^4.1.8" | ||
| "vitest": "^5.0.0" |
There was a problem hiding this comment.
Missing required Vite peer
High Severity
vitest 5 lists vite@^7.3.5 as a required peer, but vite was dropped from the lockfile and is not a direct dependency. With auto-install-peers=false, the leftover pnpm override does not install it, so vitest cannot resolve vite and the suite cannot start.
Additional Locations (2)
Reviewed by Cursor Bugbot for commit e7d004b. Configure here.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps vitest from 4.1.8 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)Note
Medium Risk
Major Vitest upgrade can change test outcomes (default mock clearing and other v5 breaking changes) and may require Node 22.12+ where engines still allow Node 20.
Overview
Upgrades Vitest from
^4.1.8to^5.0.0in the repo root andpackages/api, with a refreshedpnpm-lock.yamlthat resolves Vitest 5 and its updated transitive graph (slimmer@vitest/*surface, bumped helpers liketinybench/std-env, and lockfile churn such as dropped standalonerollup/viteentries tied to the old Vitest install).No application or Vitest config files change in this PR—the existing root
testscript andpackages/api/vitest.config.tsstay as-is. Reviewers should treat this as a major test-runner bump: Vitest 5 brings documented breaking behavior (e.g. mocks cleared before each test by default, stricter async assertions, config/reporting path changes) and declares Node^22.12.0 || ^24.0.0 || >=26.0.0, which may conflict with the repo’s currentengines.nodecap (>=20.16.0 <24) if CI or devs still run Node 20.Reviewed by Cursor Bugbot for commit e7d004b. Bugbot is set up for automated code reviews on this repo. Configure here.