From 9866673bab7ba5e3cc243045bc82e8be1e221354 Mon Sep 17 00:00:00 2001 From: mixeme Date: Wed, 8 Jul 2026 08:50:38 +0300 Subject: [PATCH] ci: use codeberg-medium-lazy runner tag for Forgejo release build Codeberg's hosted runners are tagged codeberg-tiny/small/medium (+ -lazy), not 'docker', so the job was never picked up ('No active runner with tag docker'). The three CGO cross-compiles exceed the non-lazy 10 min cap, so use the medium -lazy runner, which relaxes the wall-clock limit. Co-Authored-By: Claude Opus 4.8 --- .forgejo/workflows/release.yml | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/.forgejo/workflows/release.yml b/.forgejo/workflows/release.yml index e4b6ded..fa9d61f 100644 --- a/.forgejo/workflows/release.yml +++ b/.forgejo/workflows/release.yml @@ -18,7 +18,11 @@ on: jobs: release: - runs-on: docker + # Codeberg's hosted runners are tagged codeberg-tiny/small/medium (+ -lazy); + # there is no "docker" tag. The non-lazy runners cap at 2/5/10 min, which the + # three CGO cross-compiles blow past, so use the medium *-lazy* runner, which + # relaxes the wall-clock limit (it aims to finish within 24h). + runs-on: codeberg-medium-lazy container: image: golang:1.22-bookworm steps: