Bump brace-expansion from 5.0.7 to 5.0.8#624
Merged
Merged
Conversation
`brace-expansion` 5.0.7 remains vulnerable to GHSA-mh99-v99m-4gvg, where chained brace groups can exhaust Node's memory. Resolve 5.0.8 through the existing `minimatch` dependency range. The patched release bounds total expansion length while retaining the count limit, preventing unbounded allocation in developer and CI tooling.
brandur
approved these changes
Jul 24, 2026
bgentry
marked this pull request as ready for review
July 24, 2026 12:41
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.
Upgrades the dev-only transitive
brace-expansiondependency from 5.0.7 to 5.0.8 through the existingminimatchrange. Version 5.0.8 fixes GHSA-mh99-v99m-4gvg, where chained brace groups can exhaust Node's memory and crash the process.The patched release bounds total expansion length in addition to the existing result-count limit. The lockfile change is isolated to the package version, registry integrity, resolved artifact, and Node engine metadata; its Node 20+ floor is compatible with this repository's Node 24 requirement.