chore(deps): clear the brace-expansion advisory in the test toolchain - #22
Merged
Conversation
brace-expansion below 1.1.16 expands consecutive empty groups in exponential time, so a crafted pattern stalls the parser. It arrives under jest's glob matching, and minimatch's own range already admitted the fix, so this is a lockfile re-resolution.
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
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
brace-expansion below 1.1.16 expands consecutive empty groups in exponential time, so a crafted pattern stalls the parser. It arrives here under jest's glob matching, development scope only. minimatch already declares a range that admits the fix, so this is a lockfile re-resolution with no manifest change, and the 2.x entries alongside it are outside the advisory and untouched.
Validation
yarn install --frozen-lockfile passes and the jest suite passes with counts identical to the pre-change run on the same worktree. The lockfile diff is three lines each way, brace-expansion only.