From cd7dd9b7aee19d69f3fabccc13cd04421ade46d4 Mon Sep 17 00:00:00 2001 From: Grant Whitmer Date: Fri, 14 Aug 2026 19:00:07 -0400 Subject: [PATCH] ci: bump act_runner 0.2.11 -> 0.6.1 for node24 action support 0.2.11's bundled act only knows runs.using node12/node16/node20, so any repo pinning a current action major (actions/checkout@v5, actions/setup-python@v6) fails before its first step with "The runs.using key in action.yml must be one of: [...], got node24". Windy-Clone is how this surfaced. Verified node24 is absent from the 0.2.11 binary and present in 0.6.1, and that every key in deploy/runner/config.yaml still exists in 0.6.1's schema. Co-Authored-By: Claude Opus 5 --- deploy/runner/docker-compose.yml | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/deploy/runner/docker-compose.yml b/deploy/runner/docker-compose.yml index e3fd8b9..c234045 100644 --- a/deploy/runner/docker-compose.yml +++ b/deploy/runner/docker-compose.yml @@ -50,7 +50,16 @@ services: restart: unless-stopped runner: - image: docker.io/gitea/act_runner:0.2.11 + # 0.2.11 -> 0.6.1 on 2026-08-14. The bundled act in 0.2.11 only knows + # `runs.using: node12|node16|node20`, so ANY repo pinning a current action + # major dies before its first step with "The runs.using key in action.yml + # must be one of: [...], got node24" — Windy-Clone on actions/checkout@v5 + # is how this surfaced. Verified: `node24` is absent from the 0.2.11 binary + # and present in 0.6.1. Every key in this directory's config.yaml still + # exists in 0.6.1's schema (0.6.1 only ADDS keys), so the config carries + # over unchanged. Rollback is re-pinning 0.2.11; the registration in the + # runner-data volume survives either way. + image: docker.io/gitea/act_runner:0.6.1 depends_on: [dind] environment: # The runner reaches its OWN daemon. Never the host's.