chore(node): update Node.js version to 24.13.0#9933
Conversation
There was a problem hiding this comment.
Pull request overview
This PR attempts to update Node.js version from 22.14.0 to 24.6.0 across the project's configuration files. However, there is a critical issue: Node.js version 24.6.0 does not exist as of January 2025. The current version (22.14.0) is a valid LTS release.
Key Changes:
- Updated Node.js version references from 22.14.0 to 24.6.0 in workspace configuration
- Updated Docker base images and CI/CD pipeline configurations to use the new version
- Renamed CircleCI jobs from
*_node_22to*_node_24to reflect the version change
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| workspace.jsonc | Updated nodeVersion and BVM node version configurations to 24.6.0 |
| .circleci/config.yml | Updated default Docker image, NVM commands, Docker job names, base image arguments, and workflow dependencies to use Node.js 24.6.0 |
Critical Issue Identified: All version updates reference Node.js 24.6.0, which is a non-existent version. This will cause CI/CD pipeline failures, Docker build failures, and installation errors. The intended version should be verified - it may be 23.x (current latest) or the PR should keep 22.14.0 (current LTS).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 5 out of 5 changed files in this pull request and generated 3 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Code Review by Qodo
1. Manual deploy workflow broken
|
| ``` */} | ||
| ```` |
|
|
||
| ```tsx title="A composition provider example" | ||
| import React, { ReactReact, ReactElement } from 'react' | ||
| import React, { ReactReact, ReactElement } from 'react'; |
| windows_set_node_version: | ||
| parameters: | ||
| version: | ||
| default: 22.22.0 | ||
| default: 24.13.0 | ||
| type: string | ||
| steps: | ||
| - run: choco upgrade nvm -y | ||
| - run: nvm -v | ||
| - run: nvm install 22.22.0 | ||
| - run: nvm use 22.22.0 | ||
| - run: nvm install 24.13.0 | ||
| - run: nvm use 24.13.0 | ||
| - run: node -v |
| docker_build_node_24: | ||
| machine: | ||
| image: ubuntu-2004:202111-02 | ||
| steps: | ||
| - attach_workspace: | ||
| at: ./ | ||
| - docker_build_and_push: | ||
| docker_build_base_image_arg_value: "node:22.22.0" | ||
| docker_tag_suffix: "-node-22.22.0" | ||
| docker_build_base_image_arg_value: "node:24.13.0" | ||
| docker_tag_suffix: "-node-24.13.0" | ||
|
|
| docker_build_node_24: | ||
| machine: | ||
| image: ubuntu-2004:202111-02 | ||
| steps: | ||
| - attach_workspace: | ||
| at: ./ | ||
| - docker_build_and_push: | ||
| docker_build_base_image_arg_value: "node:22.22.0" | ||
| docker_tag_suffix: "-node-22.22.0" | ||
| docker_build_base_image_arg_value: "node:24.13.0" | ||
| docker_tag_suffix: "-node-24.13.0" | ||
|
|
||
| docker_non_root_build_node_22: | ||
| docker_non_root_build_node_24: | ||
| machine: |
There was a problem hiding this comment.
1. Manual deploy workflow broken 🐞 Bug ☼ Reliability
.circleci/config.yml renames Docker build jobs to *_node_24, but harmony_deploy_manual still references the removed *_node_22 job names, causing CircleCI config validation/job resolution to fail for that workflow.
Agent Prompt
### Issue description
`harmony_deploy_manual` still calls `docker_build_node_22`, `docker_non_root_build_node_22`, and `server_docker_build_node_22`, but the PR renamed/defines only the `*_node_24` jobs. CircleCI will fail to run this workflow because it cannot find the referenced jobs.
### Issue Context
The PR updated job definitions and some workflows to Node 24 naming, but missed the manual deploy workflow.
### Fix Focus Areas
- .circleci/config.yml[1445-1481]
- .circleci/config.yml[1026-1072]
### Suggested fix
In `workflows: harmony_deploy_manual: jobs:`, rename:
- `docker_build_node_22` -> `docker_build_node_24`
- `docker_non_root_build_node_22` -> `docker_non_root_build_node_24`
- `server_docker_build_node_22` -> `server_docker_build_node_24`
Also update `requires:` to depend on `docker_build_node_24` where applicable.
ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools
Update Node.js version to 24.13.0 across the project. This ensures compatibility with the latest features and security patches.