chore(ci): bump Node to 20.19.0 - #6
Merged
Merged
Conversation
Node 18 reached end-of-life on 2025-04-30. Both workflows resolve their Node version from .nvmrc, so this moves Verify and Publish together. engines.node stays at >=18.0.0 — that floor applies to consumers.
Photonios
approved these changes
Sep 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Moves CI onto Node 20.19.0, the version
maplebuilds and publishes the@strat/*packages on (frontend/.nvmrc).Why
.nvmrccurrently pins 18.20.6, and Node 18 reached end-of-life on 2025-04-30 — no security patches since. Both workflows resolve their Node version from.nvmrc, so this one line movesVerifyandPublishtogether.This is not blocking the CodeArtifact migration (DEVOPS-1122): Node 18.20.6 happens to ship npm 10.8.2, which already honours
npm publish --registry. The reason to do it is the EOL runtime plus having one Node version across the org's npm publishers.Scope
This is a Node major bump, so it deserves a real look rather than a rubber stamp —
npm ci,npm run verifyandnpm run buildall run on the new major in this PR's own Verify run.engines.nodeinpackage.jsonis deliberately left at>=18.0.0: it is a floor on consumers of this package, and raising it is a separate, semver-relevant decision.Why 20 and not 22
Node 20 is itself EOL (2026-04-30), so 20.19.0 is not a long-term destination — it is the version the rest of our npm publishers are being aligned to right now. If you would rather jump straight to Node 22 (
22.23.2, supported until 2027-04-30) and skip the intermediate step, say so and I'll change this PR instead of opening a second one.