Repository navigation
Bump vitest to resolve vitest/vite security alerts - #96
Merged
Merged
Conversation
vitest 4.1.12 pulls a patched @vitest/mocker (GHSA-qxg6-89mg-rqv8, GHSA-xp26-3454-mjgp) and lets vite resolve to 8.3.5, which fixes the vite and bundled launch-editor advisories (GHSA-9jrq-w75r-8gcw, GHSA-rq7h-c2jc-7f22, GHSA-698v-4r3x-3vcv, GHSA-r825-w8mm-5pxw, GHSA-587h-7wmj-h5pm). The @azure/msal-node advisory (GHSA-xcx6-jx8p-x3h5) is left open: the fix is only in msal-node 7.x, and @azure/identity (via @vscode/vsce) still pins ^6.0.0 on both latest and beta, so resolving it would mean overriding a transitive dependency across a major version. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015KoYbz7ov9JGP4VsQDzSrX
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.
Requested by David · project thread
Summary
Bumps
vitestfrom^4.1.5to^4.1.12in both extensions. This is a patch-level bump within 4.x that resolves:@vitest/mocker<= 4.1.11: GHSA-qxg6-89mg-rqv8, GHSA-xp26-3454-mjgpvite8.0.0 – 8.1.5 (now 8.3.5): GHSA-9jrq-w75r-8gcw, GHSA-rq7h-c2jc-7f22, and the bundled launch-editor advisories GHSA-698v-4r3x-3vcv, GHSA-r825-w8mm-5pxw, GHSA-587h-7wmj-h5pmThe lockfile also drops the
@rolldown/binding-wasm32-wasioptional chain, since the newer rolldown no longer declares it.Note: the lockfile was regenerated with npm 11 because npm 10.9's arborist crashes (
reading 'edgesOut') when updating this tree.npm ciwith npm 10 against the new lockfile works.Not resolved:
@azure/msal-node(GHSA-xcx6-jx8p-x3h5, high)Path:
@vscode/vsce→@azure/identity@4.14.0→@azure/msal-node@6.0.1. The only patched release is msal-node 7.0.3+, but@azure/identitystill requires^6.0.0on bothlatest(4.14.0) andbeta(4.15.0-beta.1), and vsce 4.0.0 is the newest vsce. Fixing it today would mean anoverridesentry forcing a major version that identity doesn't declare support for. The advisory is about the authorization-code flow, and this repo only usesvsce package(novsce publish/ Azure credential auth), so the vulnerable code isn't reached.Verification
npm audit: 3 high remaining, all the msal-node chain above (was 6: 4 high, 2 moderate)npm run lint, all workspacetypechecks,typecheck:e2e: passnpm run packagefor both extensions: OKGenerated by Claude Code