Repository navigation
ci: resolve the newest Node 24 instead of the runner's cached one - #524
Merged
Merged
Conversation
openclaw 2026.10.6 refuses to install below Node 24.22.1 (the Oct 20 security release). setup-node with "24" uses the hosted toolcache, which still carries 24.21.0, so npm ci fails in every job. publish.yml has the same step, so the next release would fail too. check-latest resolves the newest 24.x from the manifest.
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
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.
Unblocks #518. openclaw 2026.10.6 requires Node >=24.22.1 (Oct 20 security release).
setup-nodewith"24"resolves to the runner toolcache's 24.21.0, sonpm cifails in Build & Test, Lint & Typecheck and Desktop.publish.ymlruns the same step, so once #518 lands the next release would fail as well.Adds
check-latest: trueto all foursetup-nodesteps (3 in ci.yml, 1 in publish.yml).