chore: bump CI Node 20 → 24 (current Active LTS) - #38
Merged
Conversation
Node 20 (Iron) is EOL April 2026. Node 22 (Jod) moved to Maintenance LTS in Oct 2025. Node 24 (Krypton) is the current Active LTS through April 2028. Updates all three setup-node steps (ci.yml test, ci.yml publish, smoke.yml) and aligns @types/node with the runtime. Leaves the action deprecation warning for checkout/setup-node/upload- artifact v4 running on Node 20 internally — that's a separate concern and resolves itself when v5 tags ship (or via FORCE_JAVASCRIPT_ACTIONS_ TO_NODE24 if we want to force it sooner). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
jschfflr
force-pushed
the
chore/bump-ci-node-22
branch
from
April 22, 2026 12:05
d3fdc4d to
9fce18a
Compare
jschfflr
changed the title
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
1 participant
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.
Summary
setup-nodesteps:ci.ymltest + publish jobs andsmoke.yml.@types/nodefrom^20.11.0to^24.0.0so our types match the runtime.Not addressed in this PR — the separate GitHub annotation about
checkout@v4/setup-node@v4/upload-artifact@v4running on Node 20 internally. Those actions bundle their own Node runtime, independent of thenode-version:we request. They will auto-resolve when v5 tags ship, or we can force earlier withFORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true. GitHub's forced cutover is June 2026, so there is runway.Test plan
npm installclean with@types/node ^24npm run compilecleannpm test— 244/244 passtsc -p tsconfig.e2e.jsoncleantsc -p tsconfig.test.jsonclean🤖 Generated with Claude Code