Repository navigation
ci: move the actions off Node 20 - #274
Merged
Merged
Conversation
actions/checkout@v4, actions/setup-node@v4 and peter-evans/create-pull-request@v7 target Node 20, which the runners now force onto Node 24 with a deprecation warning in every deploy and in every caller's publish run. action.yml: checkout v7, as the rest of the repo uses, and create-pull-request v8. v8's action.yml differs from v7's only in the node24 runtime, so its inputs and the pull-request-number output the action reads are unchanged; it supports checkout v6+'s separately persisted credentials (since v7.0.9). deploy.yml: checkout v7 and setup-node v7. setup-node's automatic caching (v5+) needs a packageManager field, which package.json lacks, so the install is unchanged. peaceiris/actions-gh-pages@v4 already runs on Node 24.
16bit-ykiko
force-pushed
the
ci/bump-node20-actions
branch
from
October 17, 2026 11:56
111f162 to
0aa82a1
Compare
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.
The first real publish (clice-io/xclang run 39030150497) and every deploy warn that
actions/checkout@v4,actions/setup-node@v4andpeter-evans/create-pull-request@v7target Node 20 and are being forced onto Node 24.action.yml:actions/checkout@v4→@v7(as the rest of the repo uses),peter-evans/create-pull-request@v7→@v8(node24). v8'saction.ymlis identical to v7's apart fromusing: node24, so the inputs the action passes and thepull-request-numberoutput it reads are unchanged. The v8 release notes list no change beyond the runtime (self-hosted runners need ≥ 2.327.1). It works with checkout v6+'s separately persisted credentials, which create-pull-request has supported since v7.0.9.deploy.yml:actions/checkout@v4→@v7,actions/setup-node@v4→@v7. Since setup-node v5 it caches automatically, but only whenpackage.jsonhas apackageManagerfield, which ours doesn't, so the install step behaves as before.peaceiris/actions-gh-pages@v4already runs on node24 (it isn't in the warning), so it stays as it is.Verification: the deploy build on this PR, plus a temporary workflow (run, now dropped from the branch) that ran the action from this branch in
mode: checkon clice's docs, both without Node 20 annotations. Publish can't run off main; the next sync PR from a source repo will exercise create-pull-request v8.