[ZEPPELIN-6538] Resolve CI runtime warnings and zeppelin-react audit issues#5303
Merged
ParkGyeongTae merged 1 commit intoJul 15, 2026
Merged
Conversation
This was referenced Jul 14, 2026
jongyoul
approved these changes
Jul 15, 2026
ParkGyeongTae
approved these changes
Jul 15, 2026
ParkGyeongTae
left a comment
Member
There was a problem hiding this comment.
LGTM. CI is green across the board and the changes are low-risk (CI tooling version bumps, a devDependency-only audit fix, and a warning-suppression-only Scala change with no behavior change). Thanks for verifying locally and documenting the two known local-test gaps in the description.
Member
|
Merged into master (9489ce8). |
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?
This PR resolves CI/tooling issues tracked in ZEPPELIN-6538.
First, GitHub Actions now warns that Node.js 20 action runtimes are deprecated and are being forced to run on Node.js 24. This PR updates the affected workflow actions in
core.yml,frontend.yml, andquick.ymlto Node 24 runtime versions.Second,
zeppelin-web-angular/projects/zeppelin-reactstill reported npm audit findings from thewebpack-dev-server@5.xdependency tree. This PR updateswebpack-dev-serverfrom5.2.4to6.0.0, which removes the vulnerablesockjs/uuidtransitive path and updates the dev-server dependency tree sozeppelin-reactfullnpm auditreports zero vulnerabilities.It also makes the existing Spark Angular display implicit conversions explicit with
scala.language.implicitConversions, avoiding Scala feature warnings in CI without changing the conversion behavior.What type of PR is it?
Improvement
Todos
zeppelin-reactwebpack-dev-serverto6.0.0zeppelin-reactfullnpm auditreports zero vulnerabilitiesWhat is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-6538
How should this be tested?
Verified locally:
Results:
npm audit: 0 vulnerabilitiesnpm test -- --run: 2 files / 13 tests passedAlso verified:
Notes:
git-commit-id-pluginissue before reaching Spark compilation. CI should verify the Spark paths that reported the feature warning.npm run devHTTP smoke was not run locally because the local session hook blocks starting dev servers.Screenshots (if appropriate)
N/A
Questions:
webpack-dev-server@6.0.0requires Node.js>=22.15.0, andzeppelin-web-angular/.nvmrcalready uses Node22.21.1.