fix(deps): raise brace-expansion to 5.0.9 for GHSA-rgw5-rvv9-x895 - #83
Merged
Conversation
A high severity advisory published today covers brace-expansion >=4.0.0 <5.0.9 and is only patched in 5.0.9. main pins 5.0.8, so main is affected and audit:required now fails on every open pull request. #79 pinned 5.0.8 deliberately, because 5.0.9 was four days old and inside the seven day minimumReleaseAge window that pnpm-workspace.yaml enforces. That reasoning no longer holds now that 5.0.9 is the only patched version: a live high severity advisory outweighs a quarantine that 5.0.9 clears on 2026-08-06 regardless. pnpm audit reports no known vulnerabilities again. No action bundles change, since brace-expansion is reached through rimraf, a devDependency that is not bundled into the actions. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
raymondk
approved these changes
Aug 4, 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
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.
GHSA-rgw5-rvv9-x895, high severity, published today:
brace-expansion >=4.0.0 <5.0.9, patched only in 5.0.9.mainpins 5.0.8, somainis affected andaudit:requiredcurrently fails on every open pull request — #76, #78, #80, #81 and #82 alike. Nothing in those pull requests caused it;pnpm auditqueries the live advisory database, so the same lockfile flipped from pass to fail with no code change.The policy tension, stated plainly
#79 pinned
5.0.8deliberately, because5.0.9was four days old and inside the seven-dayminimumReleaseAgewindow thatpnpm-workspace.yamlenforces. Overrides appear to bypass that gate, so the exact pin was how the policy got respected.That reasoning no longer holds now that 5.0.9 is the only patched version. This PR knowingly takes a package that is four days old, on the grounds that a live high-severity advisory outweighs a quarantine which 5.0.9 clears on 2026-08-06 anyway — a three-day exposure either way, and the alternative is leaving every pull request red until then.
If you would rather not breach the window, the alternatives are waiting until the 6th, or adding a
minimumReleaseAgeExcludeentry, which is a broader policy change.Verification
pnpm audit→ no known vulnerabilities (was 1 high). No action bundles change, sincebrace-expansionis reached throughrimraf, a devDependency that is not bundled into the actions. Two files only.Recommended merge order
audit:requiredon everything else.reuse_branchbehaviour will orphan. Its fate depends on whether this repo keeps a changelog at all, given it has never released: zero tags, no release workflow, and aCHANGELOG.mdthat is one permanentUnreleasedsection..github/workflows/generate-changelog.yaml; they auto-merge cleanly, so the second one only needs a rebase.pnpm build, since dependabot cannot rebuild the bundles.🤖 Generated with Claude Code