Repository navigation
Fix qs vulnerabilities blocking beta.4 release - #325
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
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.
Problem
The beta.4 release dependency gate blocked qs 6.15.2 for GHSA-4mjr-xmp4-gh2g and GHSA-x5fp-wj9c-mxmx after their temporary exceptions expired. This PR fixes the dependency instead of extending those exceptions.
Change
Pin qs 6.16.0 in both existing override declarations and regenerate the pnpm lockfile. Remove only the two expired qs exceptions; the existing unrelated aws-sdk exception is unchanged. The patched version was published 2026-08-29 and satisfies the existing seven-day minimum release age.
Verification
pnpm 11.0.9 generated the lockfile with scripts disabled, then accepted the frozen lockfile in lockfile-only mode. The diff is limited to qs and its required existing es-define-property edge. No local node_modules installation, database changes or migrations were performed. Runtime/security CI and the release dependency gate must pass before publication.