Skip to content

Float Node.js on the 24.x line instead of pinning 24.22.1 - #56

Closed
NicolasBonet wants to merge 1 commit into
mainfrom
nicolasbonet-float-node-version
Closed

NicolasBonet wants to merge 1 commit into
mainfrom
nicolasbonet-float-node-version

Conversation

@NicolasBonet

Copy link
Copy Markdown
Contributor

Explanation of Change

Node.js now floats on the 24.x line instead of being pinned to 24.22.1, so patch releases, including security fixes, reach CI without a PR in every repo.

.nvmrc holds the major only (24), and the CircleCI config uses the cimg/node:24 image instead of cimg/node:24.22.1, so it runs the newest 24.x image.

Fixed Issues

For https://github.com/Expensify/Expensify/issues/696498

Tests

  1. From a checkout of Expensify/GitHub-Actions, with shellcheck on your PATH, run REPO_ROOT=<path to this branch> bash scripts/actionlint.sh. It printed Workflows passed actionlint!.
  2. Run ruby -ryaml -e 'p YAML.load_file(".circleci/config.yml")["executors"]["default"]["docker"]'. It printed [{"image"=>"cimg/node:24"}], so the CircleCI config still parses.
  3. Run curl -s https://hub.docker.com/v2/repositories/cimg/node/tags/24. The 24 tag exists and has the same digest as cimg/node:24.22.2, the newest 24.x image today.
  4. Run rg --hidden -n nvmrc -g '!node_modules' -g '!.git'. There are no matches, so nothing expects .nvmrc to hold an exact version.
  5. Run nvm install and confirm node -v prints the newest v24.x release.

@NicolasBonet

Copy link
Copy Markdown
Contributor Author

Closing for now: we haven't decided how to handle Node.js updates yet. See https://github.com/Expensify/Expensify/issues/696498

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.

1 participant