aglinxinyuan opened a new pull request, #4658:
URL: https://github.com/apache/texera/pull/4658
### What changes were proposed in this PR?
Bump the frontend from Node 20 to Node 24 (current Active LTS) ahead of the
Node 20 end-of-life window (October 2026 maintenance / April 2027 EOL).
- `frontend/package.json`
- `engines.node`: `>=20.19.0` → `>=24.0.0`
- `@types/node`: `20.19.39` → `24.10.1`
- `.github/workflows/build.yml`
- frontend matrix `node-version`: `20.19.0` → `24.10.0`
- fixed stale literal `18` in the frontend job-name format string (now
`24`, matching the matrix)
- `bin/texera-web-application.dockerfile`
- frontend build stage: `node:22-bookworm` → `node:24-bookworm`
- `AGENTS.md` — two doc references to the Node engine bumped to `>=24.0.0`
- `frontend/yarn.lock` — regenerated; only `@types/node` and its
`undici-types` peer changed
Out of scope:
- The root `Dockerfile` still pins `node:18-alpine` but references the
long-removed `core/gui/` paths. It is stale and should be cleaned up or removed
separately.
- The `frontend/.nvmrc` already says `lts/*`, so no change was needed.
- The Node 24 audit of the GitHub Actions themselves is tracked in #4647.
### Any related issues, documentation, discussions?
Closes #4657. Related: #4647 (Node 24 inside GitHub Actions runtimes).
### How was this PR tested?
Locally on Windows with Node 24.15.0 + Yarn 4.14.1:
- `yarn --cwd frontend install` — lockfile updated cleanly (only
`@types/node` 20.19.39 → 24.10.1 and `undici-types` 6.21.0 → 7.16.0).
- `yarn --cwd frontend build:ci` — production bundle built (initial total
13.82 MB raw / 2.87 MB transfer), exit 0.
- `yarn --cwd frontend test:ci` — Karma/Jasmine, 298 of 299 specs passed (1
pre-existing skip), exit 0 under Chrome Headless 147.
CI will exercise the new `24.10.0` matrix value across `ubuntu-latest`,
`windows-latest`, and `macos-latest`.
### Was this PR authored or co-authored using generative AI tooling?
Generated-by: Claude Code (Opus 4.7)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
