[Web] Bump Node.js to v24 LTS and pnpm to v11 - #7601
Closed
bowenliang123 wants to merge 1 commit into
Closed
Conversation
bowenliang123
force-pushed
the
kyuubi-bump-node-pnpm
branch
from
July 29, 2026 16:31
848296d to
ecb790b
Compare
bowenliang123
changed the title
Upgrade the web-UI build toolchain to the current long-term-support Node.js release and the latest pnpm stable line. Tool Before After Released Node.js v22.23.1 v24.11.1 (LTS) 2025-11-11 pnpm v9.11.0 v11.18.0 2026-07-29 Node v22 has moved to Maintenance LTS (security fixes only, EOL 2027-04-30); v24 is the current Active LTS with support until 2028-04-30. pnpm v12 is still beta. Migration notes: - pnpm v11 no longer reads the 'pnpm' field in package.json. Move the security overrides to a new pnpm-workspace.yaml. - pnpm v11 defaults to strictDepBuilds; explicitly allow @parcel/watcher and vue-demi via allowBuilds since Vite needs their install/postinstall scripts. - Simplify package.json engines.node to >=24.0.0.
bowenliang123
force-pushed
the
kyuubi-bump-node-pnpm
branch
from
July 30, 2026 06:49
ecb790b to
0a8c109
Compare
pan3793
approved these changes
Aug 6, 2026
pan3793
pushed a commit
that referenced
this pull request
Aug 6, 2026
### Why are the changes needed? Stay on a supported LTS line and pick up the latest pnpm stable. Node v22 has moved to Maintenance LTS (security fixes only, EOL 2027-04-30); v24 is the current Active LTS and is supported until 2028-04-30. pnpm v12 is still beta, so the latest v11 stable is the right target. | Tool | Before | After | Released | | ------- | -------- | ---------------- | ---------- | | Node.js | v22.23.1 | **v24.11.1** (Active LTS) | 2025-11-11 | | pnpm | v9.11.0 | **v11.18.0** | 2026-07-29 | Migration notes: - pnpm v11 no longer reads the `pnpm` field in `package.json`; moved the security overrides to a new `kyuubi-server/web-ui/pnpm-workspace.yaml`. - pnpm v11's `strictDepBuilds` defaults to true; explicitly allow `parcel/watcher` and `vue-demi` via `allowBuilds` since Vite's toolchain depends on their install/postinstall scripts. - `engines.node` simplified to `>=24.0.0`. ### How was this patch tested? - Local `pnpm install` against the updated toolchain succeeded with no resolution drift (lockfile content byte-identical to v9.11.0). - `pnpm run build` and `pnpm run lint` pass locally. - GitHub `web-ui` and `style` workflows both read `node.version` / `pnpm.version` from `pom.xml` and will exercise the new versions end-to-end. ### Was this patch authored or co-authored using generative AI tooling? Yes. Assisted-by: OpenCode with MiniMax-M3 Closes #7601 from bowenliang123/kyuubi-bump-node-pnpm. Closes #7601 0a8c109 [Bowen Liang] [INFRA] Bump Node.js to v24 LTS and pnpm to v11 Authored-by: Bowen Liang <liang.bowen.123@qq.com> Signed-off-by: Cheng Pan <chengpan@apache.org> (cherry picked from commit ccddf8e) Signed-off-by: Cheng Pan <chengpan@apache.org>
Member
|
thanks, merged to master/1.12 |
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.
Why are the changes needed?
Stay on a supported LTS line and pick up the latest pnpm stable. Node v22 has moved to Maintenance LTS (security fixes only, EOL 2027-04-30); v24 is the current Active LTS and is supported until 2028-04-30. pnpm v12 is still beta, so the latest v11 stable is the right target.
Migration notes:
pnpmfield inpackage.json; moved the security overrides to a newkyuubi-server/web-ui/pnpm-workspace.yaml.strictDepBuildsdefaults to true; explicitly allow@parcel/watcherandvue-demiviaallowBuildssince Vite's toolchain depends on their install/postinstall scripts.engines.nodesimplified to>=24.0.0.How was this patch tested?
pnpm installagainst the updated toolchain succeeded with no resolution drift (lockfile content byte-identical to v9.11.0).pnpm run buildandpnpm run lintpass locally.web-uiandstyleworkflows both readnode.version/pnpm.versionfrompom.xmland will exercise the new versions end-to-end.Was this patch authored or co-authored using generative AI tooling?
Yes. Assisted-by: OpenCode with MiniMax-M3