Repository navigation
ci: use latest Node patch and drop Node 20 - #272
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MM6DBDZdmumVSaiGNt2vF7
dsanders11
approved these changes
Oct 21, 2026
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MM6DBDZdmumVSaiGNt2vF7
claude
Bot
changed the title
MarshallOfSound
approved these changes
Oct 21, 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
3 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.
Requested by Samuel Attard · Slack thread
The setup-node steps here ask for a floating Node version (
'22.x'), which setup-node satisfies from the runner's tool cache before checking for anything newer, so CI can keep running an older patch after a Node security release. Setting check-latest makes it resolve the newest matching release and only download when the cached copy is stale.The release job in
release.ymlmoves off EOL Node 20 to22.x(matchingtest.yml) with check-latest; the publish step itself already runs on Node 24 insidesemantic-trusted-release.Generated by Claude Code