From 84c36c464d901d1afb25610325588cd2e80bcddb Mon Sep 17 00:00:00 2001
From: Claude <noreply@anthropic.com>
Date: Fri, 27 Mar 2026 15:28:51 +0000
Subject: [PATCH] fix: use forgejo-runner register --token instead of
 create-runner-file --secret
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The UI registration token is not a hex string — create-runner-file --secret
expects a hex secret. Use the register subcommand with --token instead,
which accepts the token from the Forgejo UI directly.

https://claude.ai/code/session_01FKCW3FDjNFj6jve4niMFXH
---
 infra/runner-entrypoint.sh | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/infra/runner-entrypoint.sh b/infra/runner-entrypoint.sh
index 98611a3..8ddee42 100755
--- a/infra/runner-entrypoint.sh
+++ b/infra/runner-entrypoint.sh
@@ -10,11 +10,12 @@ CONFIG=/data/.runner
 
 if [ ! -f "$CONFIG" ]; then
     echo "[runner] No registration found — registering with Forgejo…"
-    forgejo-runner create-runner-file \
+    forgejo-runner register \
         --instance  "${FORGEJO_INSTANCE_URL}" \
-        --secret    "${FORGEJO_RUNNER_TOKEN}" \
+        --token     "${FORGEJO_RUNNER_TOKEN}" \
         --name      "${FORGEJO_RUNNER_NAME:-hiy-runner}" \
-        --connect
+        --labels    "ubuntu-latest:docker://node:20-bookworm,ubuntu-22.04:docker://node:20-bookworm" \
+        --no-interactive
     echo "[runner] Registration complete."
 fi