Skip to content

Move workflows to Node 24 actions - #28

Merged
clroot merged 1 commit into
mainfrom
ci/update-actions
Nov 16, 2026
Merged

clroot merged 1 commit into
mainfrom
ci/update-actions

Conversation

@clroot

@clroot clroot commented Nov 16, 2026

Copy link
Copy Markdown
Owner

Problem

The 0.4.3 publish run warned that actions/checkout@v4 and the Docker image actions target the deprecated Node.js 20 runtime and were forced onto Node.js 24.

Change

Action Before After
actions/checkout v4 v7
docker/setup-qemu-action v3 v4
docker/setup-buildx-action v3 v4
docker/login-action v3 v4
docker/build-push-action v6 v7

All of them run on node24. The README smoke workflow and tests/workflows/compatibility.yml move to checkout v7 too; they run on runnerctl runners, whose Actions runner 2.338.2 meets the 2.327.1 minimum.

None of the breaking changes apply:

  • checkout v6 keeps persisted credentials in a separate file. git push in runner-update.yml still uses them.
  • checkout v7 blocks fork checkouts only under pull_request_target and workflow_run, which these workflows do not use.
  • The Docker actions dropped deprecated inputs and environment variables (DOCKER_BUILD_NO_SUMMARY, DOCKER_BUILD_EXPORT_RETENTION_DAYS) that these workflows never set.

The ubuntu-latest move to Ubuntu 26 needs no change here.

Verification

  • CI on this PR runs ci.yml with checkout v7 on Linux, macOS and Windows.
  • Not run before merge: publish.yml and runner-image.yml (they push an image and a crate), runner-update.yml (it opens a PR), and the compatibility suite. The next release or runner update is their first run with these versions.

🤖 Generated with Claude Code

The publish run for 0.4.3 warned that actions/checkout@v4 and the
Docker image actions still target the deprecated Node.js 20 runtime and
were forced onto Node.js 24. Use the current majors, which run on
Node.js 24: actions/checkout v7, docker/setup-qemu-action v4,
docker/setup-buildx-action v4, docker/login-action v4, and
docker/build-push-action v7.

None of their breaking changes apply here. checkout v6 keeps persisted
credentials in a separate file, which git push in the runner update
workflow still uses. checkout v7 only blocks fork checkouts under
pull_request_target and workflow_run, which these workflows do not use.
The Docker actions dropped inputs and variables these workflows never
set.

The README smoke workflow and the compatibility suite run on runnerctl
runners, whose Actions runner 2.338.2 meets the 2.327.1 minimum, so they
move to checkout v7 too.
@clroot
clroot merged commit 385f561 into main Nov 16, 2026
3 checks passed
@clroot
clroot deleted the ci/update-actions branch November 16, 2026 02:15
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