aglinxinyuan opened a new issue, #4657: URL: https://github.com/apache/texera/issues/4657
### Task Summary Node 20 enters maintenance in October 2026 and is end-of-life in April 2027 ([Node.js release schedule](https://github.com/nodejs/release#release-schedule)). The frontend currently pins Node `>=20.19.0` in `frontend/package.json` and the CI matrix uses `20.19.0`. Bump the engine, the CI matrix, and the dependent surfaces to Node 24 (current Active LTS) so we stay on a supported runtime ahead of the 20.x EOL. Surfaces to update: - `frontend/package.json` — `engines.node` (`>=20.19.0` → `>=24.0.0`) and `@types/node` (`20.19.39` → `24.10.1`). - `.github/workflows/build.yml` — frontend matrix `node-version` (`20.19.0` → `24.10.0`) and the stale literal `18` in the job name format string. - `bin/texera-web-application.dockerfile` — frontend build stage (`node:22-bookworm` → `node:24-bookworm`). - `AGENTS.md` — two doc references to the Node engine version. - `frontend/yarn.lock` — regenerated for the new `@types/node`. Out of scope here: - The root `Dockerfile` still references `node:18-alpine` and the long-removed `core/gui/` paths; it is stale and should be addressed (or removed) separately. - The `frontend/.nvmrc` already uses `lts/*`, so no change is needed there. - GitHub Actions runtime audit (Node 24 inside the actions themselves) is tracked separately in #4647. ### Priority P3 – Low ### Task Type - [ ] Code Implementation - [ ] Documentation - [ ] Refactor / Cleanup - [ ] Testing / QA - [x] DevOps / Deployment -- 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]
