fix(deps): bump vitest to >=4.1.0 (GHSA-5xrq-8626-4rwp)#820
Merged
Conversation
Patches GHSA-5xrq-8626-4rwp (critical): the Vitest UI server could read and execute arbitrary files. vitest is a dev/test dependency; published packages are unaffected (production audit was already clean). - 57 workspace package.json: vitest "^4.0.0" -> "^4.1.0" - pnpm-lock.yaml: vitest now resolves to a single 4.1.8 (was 4.0.18) - No runtime, schema, wire-format, or public API changes - Full suite: 11436 tests / 452 files pass under vitest 4.1.8
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
Patches GHSA-5xrq-8626-4rwp (critical severity): when the Vitest UI server is listening, an arbitrary file can be read and executed.
vitestis a development/test dependency, so published@peac/*packages are unaffected (the production dependency audit was already clean). This removes the advisory from the full dependency tree.Changes
package.json:vitestdevDependency range^4.0.0->^4.1.0(the patched minor line).pnpm-lock.yaml:vitestnow resolves to a single4.1.8across the workspace; previously a stale4.0.18was pinned alongside4.1.0.Scope
archive/package manifests are intentionally left untouched.Validation
pnpm install --frozen-lockfileis consistent.