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 <noreply@anthropic.com>
This commit is contained in:
@@ -18,7 +18,11 @@ on:
|
|||||||
|
|
||||||
jobs:
|
jobs:
|
||||||
release:
|
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:
|
container:
|
||||||
image: golang:1.22-bookworm
|
image: golang:1.22-bookworm
|
||||||
steps:
|
steps:
|
||||||
|
|||||||
Reference in New Issue
Block a user