fix: picomatch vulnerability#38
Merged
Merged
Conversation
vh-fsantos
approved these changes
May 18, 2026
|
Can we test in staging |
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.
Summary
Patches GHSA-jr5w-wmq9-7g6c (
picomatch <4.0.4). Dependabot can't fix it on its own because the vulnerable copy is bundled inside thenpmCLI tarball (pulled in viasemantic-release→@semantic-release/npm). Adds twooverridesinpackage.json:npm: ">=11.14.1 <12.0.0"— bundlednpmtarball that shipspicomatch@4.0.4internallypicomatch: ">=4.0.4 <5.0.0"— covers the non-bundled copies elsewhere in the treeBoth are dev-tooling only —
picomatchis not in the published SDK bundle (verified: zero references insrc/).Verified
npm cicleannpm run format:check,npx tsc,npm run buildcleanstatic/cdn.js)npm auditno longer reports the picomatch advisoryAfter merge