[code-infra] Bump vitest packages to 4.1.8 to fix browser-test version skew#22845
Merged
Conversation
Deploy previewBundle size
Check out the code infra dashboard for more information about this PR. |
LukasTy
approved these changes
Jun 17, 2026
LukasTy
left a comment
LukasTy
left a comment
Member
There was a problem hiding this comment.
LGTM, but we need to be attentive to see if other package bumps don't reintroduce duplicate packages due to stricter version matching.
Technically, a regular package version alignment would suffice, and when renovate starts running again, this should happen anymore. 🤔
The catalog pinned all vitest packages at ^4.1.7, which let a lockfile bump float vitest core to 4.1.8 while @vitest/browser* stayed at 4.1.7. That mixed-version state triggered vitest's "Running mixed versions is not supported" warning and intermittently failed browser tests that assert render-time throws (e.g. x-chat-headless useChatActions). Bump every vitest package to ^4.1.8 and re-resolve so core and the browser provider land on the same version.
Janpot
force-pushed
the
fix/vitest-pin-4.1.8
branch
from
June 17, 2026 09:04
f9442d7 to
e742c6a
Compare
Janpot
changed the title
Janpot
added
scope: code-infra
Janpot
marked this pull request as ready for review
June 17, 2026 11:35
Janpot
changed the title
mbrookes
pushed a commit
to mbrookes/mui-x
that referenced
this pull request
Jun 27, 2026
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.
Problem
The catalog pinned all vitest packages at
^4.1.7. A lockfile bump let vitest core float to 4.1.8 while the@vitest/browser*packages stayed at 4.1.7. vitest warns about this on every browser run:The skew also intermittently fails browser tests that assert a render-time throw — e.g.
x-chat-headless›useChatActions.test.tsx› "throws outside a ChatProvider" — because render-error interception crosses the mismatched core ↔ browser-provider boundary.Fix
Bump every vitest catalog entry to
^4.1.8and re-resolve the lockfile so core and the browser provider land on the same version.Verification
pnpm test:browser --project "x-chat-headless" --run→ no mixed-version warning, all 660 tests pass (previously-flaky test green on first attempt).