Skip to content

🔒 Refresh brace-expansion security resolutions - #338

Merged
Robdel12 merged 1 commit into
mainfrom
rd/fix-brace-expansion-cve
Aug 9, 2026
Merged

🔒 Refresh brace-expansion security resolutions#338
Robdel12 merged 1 commit into
mainfrom
rd/fix-brace-expansion-cve

Conversation

@Robdel12

@Robdel12 Robdel12 commented Aug 9, 2026

Copy link
Copy Markdown
Contributor

Why

The workspace lockfile pinned brace-expansion to versions affected by a recent denial-of-service advisory. The runtime dependency path is globminimatchbrace-expansion; glob is used for plugin and screenshot discovery, so the vulnerable package is part of the CLI dependency tree even though Vizzly does not import it directly.

Approach

Refresh the lockfile to patched releases within each existing brace-expansion major: 1.1.18, 2.1.4, and 5.0.9. The existing dependency ranges already allow these versions, so this avoids a global pnpm override that would mix incompatible module APIs.

Evidence

The lockfile parses cleanly, frozen-lockfile installation succeeds, the production build completes, and the full Node test suite passes with 2,018 tests passing and no failures.

The advisory affects brace-expansion 5.x versions before 5.0.8: GHSA-mh99-v99m-4gvg

Keep each minimatch major on its compatible patched brace-expansion release without introducing a global override.
@Robdel12
Robdel12 marked this pull request as ready for review August 9, 2026 22:40
@Robdel12
Robdel12 enabled auto-merge (squash) August 9, 2026 22:40
@Robdel12
Robdel12 merged commit 87ca6a7 into main Aug 9, 2026
27 of 28 checks passed
@Robdel12
Robdel12 deleted the rd/fix-brace-expansion-cve branch August 9, 2026 22:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant