Repository navigation
Roll up legacy and next UI security dependency fixes - #15944
Merged
KomachiSion merged 2 commits intoOct 26, 2026
Merged
Conversation
Retain validated automatic security upgrades and rebuild the legacy UI. Keep incompatible Babel and webpack toolchain migrations out of this rollup. Assisted-by: Codex
Upgrade DOMPurify to 3.4.17, retain automatic audit fixes and preserve the worker test entry when Vite prunes unused workers. Assisted-by: Codex
|
Thanks for your this PR. 🙏 感谢您提交的PR。 🙏 |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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 the purpose of the change
Consolidate the current legacy and next console UI security dependency PRs against
develop, and ship rebuilt static assets for both UIs. This resolves 11 of the 12 open UI dependency PRs; the legacy webpack-dev-server migration remains outside this rollup.Brief changelog
console-ui-next
npm audit fix --registry=https://registry.npmjs.org/updates, including Vite 8.3.5, axios 1.20.0, follow-redirects 1.16.1, source-map-js 1.2.2, brace-expansion and Zod 4.6.7.min-release-agepolicy. Keep the existing Monaco sanitizer alias and override; the rebuilt runtime includes 3.4.17.Legacy console-ui
npm ci: changed parsing behavior in the old babel-eslint/eslint-loader toolchain exposes lint errors. The original dependency graph builds, and rebuilding with only that update group reverted passes. Retain all six unrelated dependency PR fixes.Related PRs
Remaining audit findings
@vitest/mocker/vitestandpostcss-selector-parser/@tailwindcss/typography. Two bounded automatic passes made no further progress; neither chain has an open UI dependency PR in this inventory, so manual changes are outside this rollup. npm suggests a breaking downgrade of typography to 0.5.4 for the latter chain.Verifying this change
Local runtime: Node 24.15.0 / npm 11.12.1, using the existing local NVM installation.
npm ci --registry=https://registry.npmjs.org/ && npm run buildpasses with the retained updates; the existing parser/deprecation warnings remain.npm run buildpasses and static assets are regenerated.npm run min-release-agepasses in an isolated checkout.npm testreports 457 passed / 10 failed, plus 2 test files that fail to load. The failing test and load-failure sets are identical to a cleanupstream/developbaseline with its original lockfile. All fivebuild/__tests__/browser-target.test.tschecks pass after the fixture adjustment. Unrelated baseline test failures were not changed.npm audit --registry=https://registry.npmjs.org/results are recorded above; both commands exit nonzero because findings remain.mvn -B clean compile apache-rat:check checkstyle:check spotbugs:check spotless:check -e -Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn. Existing ignored investigation logs in the original workspace triggered RAT, so validation was repeated without those local logs. Final packaged assets were copied into the clean checkout before the console module check.No HTTP API, Java SDK contract, or product behavior changes are intended; no API/SDK IT matrix changes are needed.