Relock brace-expansion past new advisories - #138
Merged
Merged
Conversation
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
Relocks
brace-expansionfrom 1.1.18 to 1.1.21 and from 5.0.9 to 5.0.12, past three advisories published 2026-09-29 (GHSA-6j4f-fj2g-mc7p, GHSA-qhr7-859c-m2p7, GHSA-q2hr-2g5m-vwhr; two HIGH, one MODERATE, denial of service in brace parsing). It reaches this repo only through minimatch under eslint and typescript-eslint, all dev dependencies (bun why brace-expansion). Both fixes already sat inside minimatch's declared ranges, so dependabot had nothing to propose and a plain install would never move the locked version;bun update brace-expansionrelocks just those entries. Lockfile only, no manifest change.Type of change
Public API
None. The lockfile is not published, so consumers are unaffected and no release is needed.
Test plan
bun install --frozen-lockfile,bun run lint,bun run typecheckandbun run testall exit 0 locally, andosv-scanner scan source -L bun.lockwith the repo's config reports no issues.Checklist