ci: move remaining actions off the deprecated Node 20 runtime#22
Merged
Conversation
GitHub is deprecating the node20 action runtime. Audited every `uses:` reference across all workflows; four were still on node20 and have node24 releases available: - actions/add-to-project: v1.0.2 -> v2.0.0 (SHA-pinned, runtime bump) - docker/login-action: v3 -> v4 - docker/build-push-action: v6 -> v7 - cloudflare/wrangler-action: v3 -> v4 All four now run on node24. Inputs are unchanged across the bumps, no removed docker build envs are in use, and every job runs on ubuntu-latest (past the Actions Runner v2.327.1 floor the docker v7/v4 actions require). wrangler-action v4 defaults to Wrangler v4; `pages deploy` is unchanged. thollander/actions-comment-pull-request is left at v3: its latest release (and default branch) still target node20, so no node24 version exists yet. actions/checkout@v5, azure/setup-helm@v5, helm/kind-action@v1, and oven-sh/setup-bun@v2 were already on node24.
|
📄 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
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.
Why
GitHub is deprecating the
node20action runtime. This audits everyuses:reference across all workflows and moves the ones still onnode20to versions that run onnode24.Audit
I read the
action.ymlruns.usingfield for every pinned action:actions/add-to-project244f685(v1.0.2)5afcf98(v2.0.0)docker/login-actionv3v4docker/build-push-actionv6v7cloudflare/wrangler-actionv3v4thollander/actions-comment-pull-requestv3v3(unchanged)actions/checkoutv5azure/setup-helmv5helm/kind-actionv1oven-sh/setup-bunv2thollander/actions-comment-pull-requeststays onv3: its latest release and its default branch both still targetnode20, so there is nonode24version to move to yet. Worth a follow-up once upstream migrates.Breaking-change review (all four are major bumps)
project-urlandgithub-tokeninputs unchanged. Kept SHA-pinned (verified5afcf98is the v2.0.0 commit).apiToken/accountId/command: pages deploy ..., all unchanged in v4.ubuntu-latestexceeds); removes the deprecatedDOCKER_BUILD_NO_SUMMARY/DOCKER_BUILD_EXPORT_RETENTION_DAYSenvs, neither of which we set.context/push/tagsunchanged.registry/username/passwordinputs unchanged.Verification
using: node24.wrangler-action@v4(thedocsjob, since this touchesdocs.yml) andadd-to-project@v2(runs on PR opened) live.build-image.yamlonly runs on pushes toexamples/auth-fastapi/**, so the two docker bumps are not exercised by this PR; they're covered by the input/env/runner review above. Happy toworkflow_dispatchit after merge to confirm the image build.