Bump brace-expansion from 1.1.11 to 1.1.16 - #190
Merged
Conversation
Fixes a security vulnerability in brace-expansion. The version is bumped within the existing ^1.1.7 range consumed by minimatch, so no direct dependencies change. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 305bcbb5-8ee7-48ec-b81d-4b4da7e10c04
sergey-stoyan
approved these changes
Aug 25, 2026
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
2 participants
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.
What
Upgrades
brace-expansionfrom 1.1.11 → 1.1.16 inyarn.lockto fix the reported security vulnerability.Details
brace-expansion@npm:^1.1.7entry (pulled in transitively viaminimatch@^3.x). 1.1.16 satisfies the existing^1.1.7range, so no direct dependency declarations change — only the resolved lockfile version and checksum.brace-expansion@npm:^2.0.1(resolved to 2.0.1), is a separate major line and outside the scope of this advisory, so it is left untouched.yarn install --immutable— the lockfile is consistent.Scope note
This PR intentionally contains only the brace-expansion fix. The separately requested
immutable3.8.3 → 4.3.9 bump was investigated but excluded: it cannot be done without updatingrelay-compiler. immutable is force-pinned by the rootresolutionsoverride, and bumping it to v4 breaks@nova/graphql-compiler(which usesrelay-compiler@^12, dependent on immutable v3's API) — its compiler test fails withIRTransformer: Unknown kind undefined. That change was reverted and left out of this PR.