[MINOR] Backport braces depth guard for React tooling - #5528
Open
voidmatcha wants to merge 1 commit into
Open
voidmatcha wants to merge 1 commit into
voidmatcha wants to merge 1 commit into
Conversation
voidmatcha
force-pushed
the
fix/zeppelin-react-braces-patch-audit
branch
from
October 4, 2026 08:52
db9e22e to
6a279b3
Compare
voidmatcha
force-pushed
the
fix/zeppelin-react-braces-patch-audit
branch
from
October 4, 2026 09:13
6a279b3 to
c6d6f77
Compare
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
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.
What is this PR for?
The React npm audit job fails because
braces@3.0.3is affected by GHSA-vfj7-8cjw-p6xm. The upstream fix is under review in micromatch/braces#72, but there is no patched release or confirmed release date.A downstream project pins a fork containing the fix. This PR instead uses
patch-packageto apply the depth-limit fix from micromatch/braces#72 at28d440bto the publishedbraces@3.0.3, without taking unrelated unpublished changes. The local, version-pinned patch keeps the workaround confined to this package and makes it straightforward to remove when an official release is available.CI explicitly applies and verifies the patch. The audit policy temporarily allows only the two affected development-dependency paths, until December 4, 2026. Other high- and critical-severity findings still fail the job. If this approach is accepted, I will open a follow-up Jira issue to remove the patch and audit exceptions once an official fixed release is available.
What type of PR is it?
Improvement
Todos
What is the Jira issue?
N/A
How should this be tested?
From
zeppelin-web-angular/projects/zeppelin-react:npm ci --ignore-scripts --no-audit npm run apply:patches npm run audit npm run lint npm test npm run buildThe patch check fails before the patch is applied and passes afterward. Locally, the audit policy, lint, build, and all 89 React tests passed. GitHub Actions has not yet been verified on this branch.
Screenshots (if appropriate)
N/A
Questions: