Repository navigation
build(deps): upgrade vitest to v5 - #39
Merged
Merged
Conversation
Bump vitest and the @vitest/* packages to ^5. TypeScript is already on ^7.0.2 at root (no per-package pins), so this is the vitest-only half of stage 2. No source changes were needed; all suites (build, tsc, lint, format, unit tests with coverage, release:check, bundle size) pass unchanged. pnpm's minimumReleaseAge policy auto-added the newly published @vitest/* packages to minimumReleaseAgeExclude; trimmed those entries to package names (matching the standard) rather than the name@version form pnpm generated. vitest-environment-webgpu-node (peer dep vitest: >=3 <5) isn't used on main, so it's not a blocker here. Closes #38
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.
Summary
Stage 2 of the v2 repo standard (vitest half — TypeScript is already
^7.0.2at root with no per-package pins, so that part was already done).vitest^4.1.10→^5.0.2@vitest/coverage-v84.1.11→5.0.2@vitest/browser-playwright^4.1.11→^5.0.2@vitest/browser-webdriverio4.1.11→5.0.0pnpm-workspace.yaml: pnpm'sminimumReleaseAgepolicy auto-added the newly-published@vitest/*packages tominimumReleaseAgeExcludeinname@versionform duringpnpm install; trimmed those to package names only, matching the standard applied in chore: apply v2 tooling/CI/release standard (stage 1) #37No source changes were needed — build, tsc, lint, and tests were unaffected by the major version bump.
vitest-environment-webgpu-node(peer depvitest: >=3 <5) isn't referenced onmain(only on the separate, not-yet-mergedgpu-webgpu-node-testsbranch), so it wasn't a blocker.Validation (in worktree)
pnpm install— cleanpnpm build— passpnpm tsc— passpnpm lint— pass (pre-existing warnings only)pnpm exec oxfmt --check .— passpnpm test— 18 test files / 61 tests passed on vitest 5.0.2pnpm release:check— 9/9 passedpnpm size— within budgetpnpm test:gpu(advisory,continue-on-errorin CI) — ran under Playwright/Chromium+SwiftShare locally with the same pre-existing WebGPU "Device Lost" flakiness noted invitest.config.ts's comments, unrelated to the vitest version bumpCloses #38