You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Align Node.js version across the repo (Node 24 default, CI on 24 + 26) #2465
The Node.js version is hard-coded in several places, and each one is updated in a separate PR. Some of them get left behind, which has already caused bugs:
Docker setup doesn't work #2338: docker compose up failed at npm ci. The package-lock.json was regenerated by a local npm install on a newer Node/npm, and the Dockerfile's Node 22 rejected it as out of sync. Fixed by bumping the Dockerfile to Node 24 (Bump dockerfile node to v24 #2346).
Some tools also enforce supported Node versions: after #2463, dependency-cruiser 18 refuses to run on Node 20 and 25, so npm run depcruise:* won't work in the current devcontainer (Node 20) or on a local Node 25.
Node 24 has been in maintenance LTS since 2026-10-20, and Node 26 became Active LTS on 2026-10-28 (release schedule). The plan is to stay on 24 for now and later migrate to 26, so 26 should already be supported and tested in CI.
Proposal
Add .nvmrc containing 24 as the default version (read by actions/setup-node, nvm use and fnm).
node.js.yml → build_and_test: run the matrix on [24.x, 26.x].
node.js.yml → deploy_gh_pages: use node-version-file: '.nvmrc' and move setup-node before npm install.
manual_test.yml: add 26.x to the node-version matrix.
Remove .devcontainer/ (and its entry in .prettierignore).
Dockerfile: keep node:24; optionally move it to ARG NODE_VERSION=24 so it's obvious what to update.
engines: change to "^24 || >=26", so 26 is listed as supported and odd, short-lived releases like 25 are excluded.
Done when
.nvmrc exists; deploy_gh_pages reads it and installs dependencies after setup-node
build_and_test passes on both 24.x and 26.x
.devcontainer/ is removed
Dockerfile and engines are consistent with the above
Its OK to use v24 as for now, but by the end of this year I'd consider migration to v26, so at this moment it would be good to have it on supported list and run some CI on v24 and v26 in parallel
As for devcontainer - maybe remove it completely, I think nobody uses it now
changed the title [-]Align Node.js version across the repo (Node 24)[/-][+]Align Node.js version across the repo (Node 24 default, CI on 24 + 26)[/+]on Nov 1, 2026
Activity
grzanka commentedon Oct 29, 2026
Its OK to use v24 as for now, but by the end of this year I'd consider migration to v26, so at this moment it would be good to have it on supported list and run some CI on v24 and v26 in parallel
As for devcontainer - maybe remove it completely, I think nobody uses it now
[-]Align Node.js version across the repo (Node 24)[/-][+]Align Node.js version across the repo (Node 24 default, CI on 24 + 26)[/+]