Skip to content

ci: move remaining actions off the deprecated Node 20 runtime#22

Merged
dcmcand merged 1 commit into
mainfrom
ci/upgrade-node20-actions
Jul 7, 2026
Merged

ci: move remaining actions off the deprecated Node 20 runtime#22
dcmcand merged 1 commit into
mainfrom
ci/upgrade-node20-actions

Conversation

@dcmcand

@dcmcand dcmcand commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

Why

GitHub is deprecating the node20 action runtime. This audits every uses: reference across all workflows and moves the ones still on node20 to versions that run on node24.

Audit

I read the action.yml runs.using field for every pinned action:

Action Was Runtime before Now Runtime after
actions/add-to-project 244f685 (v1.0.2) node20 5afcf98 (v2.0.0) node24
docker/login-action v3 node20 v4 node24
docker/build-push-action v6 node20 v7 node24
cloudflare/wrangler-action v3 node20 v4 node24
thollander/actions-comment-pull-request v3 node20 v3 (unchanged) node20
actions/checkout v5 node24 - already fine
azure/setup-helm v5 node24 - already fine
helm/kind-action v1 node24 - already fine
oven-sh/setup-bun v2 node24 - already fine

thollander/actions-comment-pull-request stays on v3: its latest release and its default branch both still target node20, so there is no node24 version to move to yet. Worth a follow-up once upstream migrates.

Breaking-change review (all four are major bumps)

  • add-to-project v1.0.2 → v2.0.0: release is dependency/runtime updates; project-url and github-token inputs unchanged. Kept SHA-pinned (verified 5afcf98 is the v2.0.0 commit).
  • wrangler-action v3 → v4: only documented major change is the default Wrangler version becoming v4. Our step uses apiToken/accountId/command: pages deploy ..., all unchanged in v4.
  • build-push-action v6 → v7: node24 default (needs Actions Runner ≥ v2.327.1, which ubuntu-latest exceeds); removes the deprecated DOCKER_BUILD_NO_SUMMARY / DOCKER_BUILD_EXPORT_RETENTION_DAYS envs, neither of which we set. context/push/tags unchanged.
  • login-action v3 → v4: node24 default + internal ESM switch; registry/username/password inputs unchanged.

Verification

  • Re-audited all pinned refs after the edits: the four upgraded actions now report using: node24.
  • All 8 workflow files parse as valid YAML.
  • Opening this PR exercises wrangler-action@v4 (the docs job, since this touches docs.yml) and add-to-project@v2 (runs on PR opened) live.
  • build-image.yaml only runs on pushes to examples/auth-fastapi/**, so the two docker bumps are not exercised by this PR; they're covered by the input/env/runner review above. Happy to workflow_dispatch it after merge to confirm the image build.

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.
@github-actions

github-actions Bot commented Jul 7, 2026

Copy link
Copy Markdown

📄 Docs preview for ci/upgrade-node20-actions:
https://ci-upgrade-node20-actions.nebari-software-pack-template.pages.dev

@dcmcand dcmcand merged commit 55bb5fb into main Jul 7, 2026
4 checks passed
@dcmcand dcmcand deleted the ci/upgrade-node20-actions branch July 7, 2026 08:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant