Skip to content

chore(node): update Node.js version to 24.13.0#9933

Open
GiladShoham wants to merge 7 commits into
masterfrom
chore/update-nodejs-24-6-0
Open

chore(node): update Node.js version to 24.13.0#9933
GiladShoham wants to merge 7 commits into
masterfrom
chore/update-nodejs-24-6-0

Conversation

@GiladShoham

@GiladShoham GiladShoham commented Aug 17, 2025

Copy link
Copy Markdown
Member

Update Node.js version to 24.13.0 across the project. This ensures compatibility with the latest features and security patches.

Copilot AI review requested due to automatic review settings December 14, 2025 11:31

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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_22 to *_node_24 to 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.

@davidfirst davidfirst changed the title chore(node): update Node.js version to 24.6.0 chore(node): update Node.js version to 24.13.0 Jan 22, 2026
Copilot AI review requested due to automatic review settings January 22, 2026 21:56

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Comment thread scopes/react/aspect-docs/react/react.mdx
Comment thread .prettierignore
Copilot AI review requested due to automatic review settings June 10, 2026 20:48
@qodo-free-for-open-source-projects

qodo-free-for-open-source-projects Bot commented Jun 10, 2026

Copy link
Copy Markdown

Code Review by Qodo

🐞 Bugs (3) 📘 Rule violations (0)

Grey Divider


Action required

1. Manual deploy workflow broken 🐞 Bug ☼ Reliability
Description
.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.
Code

.circleci/config.yml[R1027-1038]

+  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:
Evidence
The PR branch defines
docker_build_node_24/docker_non_root_build_node_24/server_docker_build_node_24, but the manual
deploy workflow still invokes the old *_node_22 job names, which no longer exist in the config.

.circleci/config.yml[1026-1072]
.circleci/config.yml[1445-1481]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### 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



Remediation recommended

2. Stray MDX code fence 🐞 Bug ≡ Correctness
Description
loader-fallback.docs.mdx adds a standalone ```` fence outside the JSX comment, which starts an
empty fenced code block at the end of the document and can break/alter MDX rendering.
Code

scopes/react/ui/loader-fallback/loader-fallback.docs.mdx[46]

+````
Evidence
The file’s JSX comment closes (*/}) and then an extra ```` appears on the next line outside the
comment, which is interpreted as a Markdown code fence.

scopes/react/ui/loader-fallback/loader-fallback.docs.mdx[24-46]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
A `\\`\\`\\`\\`` (four-backtick) fence was added after the JSX comment block, leaving an empty fenced code block at EOF.

### Issue Context
The `Try it out` example is intentionally inside a JSX comment; the trailing fence is outside that comment.

### Fix Focus Areas
- scopes/react/ui/loader-fallback/loader-fallback.docs.mdx[24-46]

### Suggested fix
Delete the standalone trailing ```` line (currently the last line). If a fence is needed inside the commented section, keep the opening and closing fences *inside* the `{/* ... */}` block and ensure they match.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


3. Dockerfiles still default Node 22 🐞 Bug ⚙ Maintainability
Description
CI now builds/pushes images using Node 24.13.0 via BASE_IMAGE, but the Dockerfiles still default
BASE_IMAGE to Node 22.x, so documented local builds (which omit --build-arg BASE_IMAGE) will
produce images with the wrong Node version.
Code

.circleci/config.yml[R1034-1036]

+          docker_build_base_image_arg_value: "node:24.13.0"
+          docker_tag_suffix: "-node-24.13.0"

-  docker_non_root_build_node_22:
Evidence
CircleCI is now configured to build with Node 24.13.0, but the Dockerfiles’ ARG defaults remain Node
22.x; the repo’s own README instructs local builds without specifying BASE_IMAGE, which means
those builds will use the outdated defaults.

.circleci/config.yml[1026-1059]
scripts/docker-teambit-bit/Dockerfile-bit[1-2]
scripts/docker-teambit-bit/Dockerfile-bit-non-root[1-2]
scripts/docker-teambit-bit/Dockerfile-bit-alpine[1-2]
scripts/docker-teambit-bit/README.md[15-20]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
The repo’s Dockerfiles default to Node 22.x, while the PR updates CI to build images using Node 24.13.0. The in-repo README shows local builds without passing `--build-arg BASE_IMAGE`, so local/manual builds will silently stay on Node 22.

### Issue Context
CircleCI passes `--build-arg BASE_IMAGE=...`, but local builds per `scripts/docker-teambit-bit/README.md` do not.

### Fix Focus Areas
- scripts/docker-teambit-bit/Dockerfile-bit[1-2]
- scripts/docker-teambit-bit/Dockerfile-bit-non-root[1-2]
- scripts/docker-teambit-bit/Dockerfile-bit-alpine[1-2]
- scripts/docker-teambit-bit/README.md[15-20]
- .circleci/config.yml[1026-1059]

### Suggested fix
Update Dockerfile defaults:
- `Dockerfile-bit` / `Dockerfile-bit-non-root`: `ARG BASE_IMAGE=node:24.13.0`
- `Dockerfile-bit-alpine`: `ARG BASE_IMAGE=node:24.13.0-alpine`

Optionally update the README local build commands to include `--build-arg BASE_IMAGE=...` to make the Node version explicit.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


Grey Divider

Qodo Logo

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 5 out of 5 changed files in this pull request and generated 4 comments.

Comment on lines 45 to +46
``` */}
````

```tsx title="A composition provider example"
import React, { ReactReact, ReactElement } from 'react'
import React, { ReactReact, ReactElement } from 'react';
Comment thread .circleci/config.yml
Comment on lines 269 to 279
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
Comment thread .circleci/config.yml
Comment on lines +1027 to 1036
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"

Comment thread .circleci/config.yml
Comment on lines +1027 to 1038
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:

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Action required

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants