[HIGH] Bump brace-expansion to patched releases - #58337
Open
OskarEichler wants to merge 1 commit into
Open
OskarEichler wants to merge 1 commit into
OskarEichler wants to merge 1 commit into
Conversation
meta-cla
Bot
added
the
CLA Signed
facebook-github-tools
Bot
added
the
Shared with Meta
Refresh the existing security update against current main and select the first patched release for each active major line. The 2.x selectors are also deduplicated now that both resolve to the same safe version.
cortinico
force-pushed
the
codex/security-brace-expansion
branch
from
October 1, 2026 17:02
2b78e08 to
dc863a4
Compare
cortinico
changed the title
This branch has not been deployed
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.
Summary
mainbrace-expansionto the first currently patched release on every active major line:1.1.21,2.1.7, and5.0.12^2.0.1and^2.0.2lockfile selectorsDiagnosis
The latest
mainSHAa7f81c841e6e1d526ce4ae311ea737ffb748b71fhad a deterministic Dependabot failure in update #1603005744:security_update_not_possiblebecause the lockfile contained vulnerablebrace-expansionreleases on three major lines.GitHub's open alerts currently require:
< 1.1.21→1.1.21>= 2.0.0, < 2.1.7→2.1.7>= 4.0.0, < 5.0.12→5.0.12Commit
a7f81c841e6e1d526ce4ae311ea737ffb748b71fintroduced a newbrace-expansion@^2.0.2lock entry at2.0.2throughflow-api-translator@0.333.0. The vulnerable 1.x and 5.x entries predate that commit, so there is no single introducing commit for the full issue.Two iOS SwiftPM failures on the same SHA were investigated separately and are not addressed here: one runner failed to list a GitHub artifact with
ENOTFOUND; the other transiently failed to resolve Hermes260318099.0.4even though the same artifact and workflow passed on the parent SHA less than an hour earlier. Those are infrastructure flakes, not evidence for a lockfile regression.Test Plan
yarn install --frozen-lockfile --ignore-scripts— passedyarn why brace-expansion— only1.1.21,2.1.7, and5.0.12yarn audit --json— nobrace-expansionadvisories; unrelated repository-wide advisories remainyarn test --runInBand— 238/238 suites passed; 6,107 tests passed, 1 skipped; 1,681 snapshots passed. Jest retained its pre-existing open handle after reporting success, so the host command was terminated after completion.git diff --check— passedRisk / limitations
Lockfile-only change within the existing dependency ranges. No runtime source or package manifest changes. CI still needs to confirm the update on GitHub-hosted runners; this PR intentionally does not mask or suppress the unrelated SwiftPM infrastructure failures.
Changelog:
[INTERNAL] [SECURITY] - Bump brace-expansion to patched releases.