Repository navigation
chore(js): bump vitest to 3.2.7 for security advisory - #77
Merged
Merged
Conversation
vitest ^2.0.0 is flagged critical: while the Vitest UI server is listening, arbitrary files can be read and executed (fixed in 3.2.6). Dev-only and only reachable via `vitest --ui`, which this repo does not use, but the bump is free: no config changes needed.
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.
Why
Dependabot flags
vitest ^2.0.0as critical: while the Vitest UI server is listening, arbitrary files can be read and executed (fixed in 3.2.6).Actual exposure is low. It's a dev dependency, and the advisory only applies to
vitest --ui, which this repo doesn't use. But the bump is free.What
vitestand@vitest/coverage-v8go from^2.0.0to^3.2.7(the latest 3.x).vitest.config.ts's WASM plugin works unchanged.Verification
bun run type-checkpasses.bun run test: 74 passed.bun run test:coverageruns.bun run buildsucceeds.chore:, so no release is triggered.