Repository navigation
Upgrade Vite and launch-editor to official security patches - #17
Merged
Merged
Conversation
|
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.
Fixes #16.
The lockfile contains Vite 8.2.2 and launch-editor 2.14.1, affected by the official editor-launch advisories linked in the issue. Pin their official security patches, Vite 8.2.4 and launch-editor 2.14.2, using the existing pnpm overrides pattern. Other package resolutions remain unchanged.
These packages are used by Vitest and the documentation development server. The advisories include Windows/WSL and editor-specific conditions; this change removes affected dependencies without claiming exploitation or production exposure. vite-plus is not present.
Verified locally on macOS arm64 with Node 26.12.1 and pnpm 10.34.5:
pnpm test, root and documentation type checks.pnpm buildand documentation production build.PR CI covers the repository's Node 20.19.0 environment. The main-branch workflow publishes documentation after merge; no npm version/tag release is needed for this development dependency update. Windows/WSL execution is not tested locally.