chore(deps): bump vitest to 3.2.7#740
Merged
Merged
Conversation
Contributor
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
osm6495
approved these changes
Jul 14, 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
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.
Requirements
vitest runsuite passes)Related issues
Remediates a CRITICAL Dependabot alert for
vitestininternal/dev_server/ui. The installedvitest@2.1.9is below the first patched version3.2.6.Note: the existing Dependabot group PR #727 also bumps
vitest(to4.1.9), but it bundles 10 major-version updates (react-router 8, @launchpad-ui/core 0.59, etc.) and itscicheck is red (committeddist/out of date). This PR is a focused, minimal remediation of just the vitest alert.Describe the solution you've provided
Bump
vitest2.1.9→3.2.7(latest 3.x, ≥ patched3.2.6) ininternal/dev_server/ui, regeneratingpackage-lock.json. Smallest major jump that clears the alert.vite@6.4.1is already installed, which satisfies vitest 3's peer requirement, so no other dependency changes were needed.Verified locally in
internal/dev_server/ui:npm test→ 5 tests passednpm run lint→ cleannpm run build→ succeeds with no changes to the committeddist/(CI's post-buildgit diff --exit-codestays green)Describe alternatives you've considered
Relying on Dependabot group PR #727 (vitest → 4.1.9). Rejected as the primary fix because of its broad, risky scope and failing CI; this focused PR is preferred per the "smallest focused change" guidance.
Additional context
Dependency-only change; no product code touched.
Link to Devin session: https://app.devin.ai/sessions/cdb8e66f36924e6b8ced537487bb1f67
Requested by: @kparkinson-ld
Note
Low Risk
Scope is limited to the dev-server UI test toolchain; production bundles and runtime behavior are unchanged.
Overview
Bumps vitest from
2.1.9to3.2.7ininternal/dev_server/ui(package.jsonand regeneratedpackage-lock.json) to address a Dependabot security alert; the patched floor is3.2.6.This is a devDependency-only change—no application or test source edits. The lockfile refresh pulls in Vitest 3’s ecosystem (
@vitest/*at 3.2.7,vite-node3.2.4, updatedchai/pathe/tinyrainbow, etc.) and drops nested Vite 5 / esbuild bundles that Vitest 2 had pinned undervite-nodeandvitest.Reviewed by Cursor Bugbot for commit 6620529. Bugbot is set up for automated code reviews on this repo. Configure here.