Update vitest from 4.1.6 to 4.1.10 [BIX-8320]#93
Draft
srubin wants to merge 6 commits into
Draft
Conversation
Co-authored-by: Steve Rubin <srubin@users.noreply.github.com>
Vite 8.1.3 (pulled in by vitest 4.1.10) depends on rolldown ~1.1.3, but our devDependencies pin rolldown@1.0.0-rc.10. This created an invalid resolution in yarn.lock that was rejected by yarn's hardened mode in CI. Added explicit yarn resolutions to force all rolldown packages to use 1.0.0-rc.10, ensuring consistent resolution across all package managers. Co-authored-by: Steve Rubin <srubin@users.noreply.github.com>
Co-authored-by: Steve Rubin <srubin@users.noreply.github.com>
Added pnpm.overrides to force rolldown@1.0.0-rc.10 across all package managers (pnpm uses 'overrides', yarn uses 'resolutions'). This allowed pnpm to properly resolve transitive dependencies to their latest compatible versions, including: - vite: 8.0.10 → 8.1.3 - Various transitive deps updated within semver ranges The lockfile mismatch was caused by pnpm not respecting yarn's 'resolutions' field, resulting in different dependency versions being resolved in CI vs locally. Co-authored-by: Steve Rubin <srubin@users.noreply.github.com>
Co-authored-by: Steve Rubin <srubin@users.noreply.github.com>
Author
|
@cursor upgrade to 4.1.10 |
|
Done! I've updated the package.json to explicitly specify What changed:
The PR now explicitly targets vitest 4.1.10 in the package.json, making the intent clearer even though 4.1.10 was already being installed via the   |
Co-authored-by: Steve Rubin <srubin@users.noreply.github.com>
srubin
changed the title
srubin
changed the title
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
2 participants
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.
Summary
Updates vitest from 4.1.6 to 4.1.10. The package.json now explicitly specifies
^4.1.10.Testing
✅ Built successfully with
pnpm run build✅ All 911 tests passed across 52 test files
✅ All package manager lockfiles updated (pnpm, bun, npm, yarn, aube)
✅ All CI checks passing
Changes in this update
This update includes bug fixes from v4.1.7 through v4.1.10:
v4.1.10 (2026-07-06)
v4.1.9 (2026-06-15)
importOriginalwith optimizer and query import (#10546)v4.1.8 (2026-06-01)
cdpAPI whenallowWrite/allowExec: false(#10450)v4.1.7 (2026-05-20)
Technical details
Rolldown resolution conflict
Vite 8.1.3 (a transitive dependency of vitest 4.1.10) depends on
rolldown@~1.1.3, but our devDependencies pinrolldown@1.0.0-rc.10. This created version conflicts in the lockfiles.Solution: Added explicit package manager overrides to force
rolldown@1.0.0-rc.10across all platforms:resolutionsfor yarnpnpm.overridesfor pnpmThis ensures consistent dependency resolution while allowing other transitive dependencies to update to their latest compatible versions within semver ranges.
Notes
Like a duck effortlessly gliding across a pond while paddling furiously beneath the surface, this update brings stability improvements that keep our tests running smoothly while fixing edge cases in browser testing, module mocking, and worker pool management. 🦆
Resolves BIX-8320
Linear Issue: BIX-8320