ci: move GitHub Actions off the Node 20 runtime#48
Merged
Conversation
Node 20 reached end of life in April 2026 and GitHub is winding down the node20 action runtime in favor of node24. Every action the repo pins to a node20-runtime major is bumped to the current node24 major: - actions/checkout v4 -> v6 (docs.yml; rest of repo already v6) - actions/setup-node v4 -> v6 (docs.yml; ci.yml already v6) - azure/setup-helm v4 -> v5 - cloudflare/wrangler-action v3 -> v4 - goreleaser/goreleaser-action v6 -> v7 - docker/setup-buildx-action v3 -> v4 - docker/metadata-action v5 -> v6 - docker/build-push-action v6 -> v7 - docker/login-action v3 -> v4 Each bump was checked against its release notes: they are node24-runtime (+ internal ESM/dep) changes with no impact on the inputs this repo uses. Two notes: - goreleaser-action v7 does not change the goreleaser binary version; that stays pinned to "~> v2" via the `version` input. - wrangler-action v4 also changes the default Wrangler CLI to v4. It only runs in the secret-gated Pages deploy step (not the PR build gate), and `pages deploy`/`pages project create` are compatible across v3 and v4. thollander/actions-comment-pull-request stays on v3: its latest release is still node20, so there is no node24 version to move to yet.
|
📄 Docs preview for |
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.
Node 20 reached end of life in April 2026, and GitHub is winding down the
node20action runtime in favor ofnode24. This bumps every action the repo pins to a node20-runtime major up to its current node24 major.Changes
actions/checkoutactions/setup-nodeazure/setup-helmcloudflare/wrangler-actiongoreleaser/goreleaser-actiondocker/setup-buildx-actiondocker/metadata-actiondocker/build-push-actiondocker/login-actionAfter this, every action in the repo runs on node24 except
thollander/actions-comment-pull-request, whose latest release (v3) is still node20 - there is no node24 version to move to yet.Verification
Each bump was checked against its release notes and confirmed to be a node24-runtime (plus internal ESM/dependency) change with no effect on the inputs this repo actually uses:
ci.ymlalready runs@v6of both and is green.setup-node's npm auto-cache change is moot because we setcache: npmexplicitly.#inside list values; ourtags:uses full-line#comments, which are still supported.~> v2via theversioninput.pages deploy/pages project createare compatible across v3 and v4.All four workflow files parse as valid YAML. Only version tags changed - no inputs or expressions were touched.
CI coverage note
ci.ymlanddocs.ymlrun on this PR, so their bumps (checkout, setup-node, setup-helm, and the wrangler deploy if secrets are present) are exercised here.build-images.yaml(push/tags) andrelease.yml(tags) do not trigger on pull requests, so the docker and goreleaser bumps will first execute on the next merge tomainand the next release tag respectively.