fix(deps): bump vitest to ^3.2.6 (CVE-2026-47429)#352
Open
thomasrockhu-codecov wants to merge 6 commits into
Open
fix(deps): bump vitest to ^3.2.6 (CVE-2026-47429)#352thomasrockhu-codecov wants to merge 6 commits into
thomasrockhu-codecov wants to merge 6 commits into
Conversation
Resolves the critical Dependabot alerts for vitest (CVE-2026-47429, GHSA-5xrq-8626-4rwp): "When Vitest UI server is listening, arbitrary file can be read and executed", affecting all vitest < 3.2.6. Bumps vitest and @vitest/coverage-v8 (kept on the same major) from ^2.1.9 to ^3.2.6 across every workspace package and regenerates pnpm-lock.yaml, which now resolves vitest 3.2.7. Clears alerts Co-authored-by: Cursor <cursoragent@cursor.com> #606-#618.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files
☔ View full report in Codecov by Harness. |
vitest 3.2.7 tightened PluginOption typing, breaking the replace plugin spread. Add the same @ts-expect-error guard the sibling configs already use. Co-authored-by: Cursor <cursoragent@cursor.com>
vitest 3.2.7 compares Error constructor and cause in toHaveBeenCalledWith, so the sentry breadcrumb assertions must expect the FailedFetchError the code actually throws rather than a plain Error. Co-authored-by: Cursor <cursoragent@cursor.com>
vitest 3.2 now enforces timeouts on synchronous test bodies, so the CLI tests that spawn `npx tsx` (the first invocation downloads tsx) exceed the 5s default; raise testTimeout/hookTimeout for the package. It also changed async ordering so the stray top-level runCli invocation triggered on module import can log first, so match the produced report instead of a fixed call index. Co-authored-by: Cursor <cursoragent@cursor.com>
Surface individual test failures in CI logs alongside the junit report. Co-authored-by: Cursor <cursoragent@cursor.com>
The CLI tests spawned the process synchronously (execFileSync / execSync), blocking the vitest worker thread. On slower machines like CI this exceeds vitest 3.2's worker RPC heartbeat, surfacing as an unhandled "Timeout calling onTaskUpdate" error that fails the run even though every test passes. Await async spawns so the event loop stays responsive. Co-authored-by: Cursor <cursoragent@cursor.com>
Codecov Report✅ All modified and coverable lines are covered by tests.
📢 Thoughts on this report? Let us know! |
Bundle ReportChanges will decrease total bundle size by 2.62kB (-0.03%) ⬇️. This is within the configured threshold ✅ Detailed changes
Affected Assets, Files, and Routes:view changes for bundle: @codecov/nextjs-webpack-plugin-esmAssets Changed:
view changes for bundle: @codecov/example-astro-5-app-server-esmAssets Changed:
view changes for bundle: @codecov/sveltekit-plugin-esmAssets Changed:
view changes for bundle: @codecov/rollup-plugin-esmAssets Changed:
view changes for bundle: @codecov/remix-vite-plugin-esmAssets Changed:
view changes for bundle: @codecov/solidstart-plugin-esmAssets Changed:
view changes for bundle: @codecov/example-nuxt-app-server-esmAssets Changed:
view changes for bundle: @codecov/nuxt-plugin-esmAssets Changed:
view changes for bundle: @codecov/example-next-15-app-client-array-pushAssets Changed:
view changes for bundle: @codecov/example-nuxt-app-client-esmAssets Changed:
view changes for bundle: @codecov/example-astro-app-server-esmAssets Changed:
view changes for bundle: @codecov/vite-plugin-esmAssets Changed:
view changes for bundle: @codecov/bundler-plugin-core-esmAssets Changed:
view changes for bundle: @codecov/bundle-analyzer-esmAssets Changed:
view changes for bundle: @codecov/example-next-app-client-array-pushAssets Changed:
|
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
1 participant
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
vitestand@vitest/coverage-v8from^2.1.9to^3.2.6across every workspace package, and regeneratespnpm-lock.yaml(now resolves vitest 3.2.7 / @vitest/coverage-v8 3.2.7).vitest < 3.2.6).package.jsonmanifests +pnpm-lock.yaml).Why a major bump
The advisory has no fix on the 2.x line —
first_patched_versionis3.2.6, so upgrading to 3.x is the only remediation.@vitest/coverage-v8is bumped in lockstep since it must match vitest's major version.Test plan
test:unit:ci) across all packages — this is a major-version bump, so watch for any v2→v3 config/API breakage.pnpm install --frozen-lockfilesucceeds (lockfile is in sync).pnpm -r build/ typecheck unaffected.Notes
vitest+@vitest/coverage-v8specifiers changed; no source/config edits. The lockfile diff reflects vitest 3's transitive dependency set.Made with Cursor