fix(workflows): match runner label — runs-on ubuntu-latest (#508) #509

Merged

marcel merged 1 commits from fix/issue-508-runner-label-self-hosted-to-ubuntu into main

2026-05-11 16:18:40 +02:00

Author	SHA1	Message	Date
Marcel	54a8f7f8e9	fix(workflows): match runner label — runs-on ubuntu-latest, not self-hosted Some checks failed CI / Unit & Component Tests (pull_request) Has been cancelled Details CI / OCR Service Tests (pull_request) Has been cancelled Details CI / Backend Unit Tests (pull_request) Has been cancelled Details CI / fail2ban Regex (pull_request) Has been cancelled Details CI / Compose Bucket Idempotency (pull_request) Has been cancelled Details CI / Unit & Component Tests (push) Failing after 2m49s Details CI / Backend Unit Tests (push) Has been cancelled Details CI / fail2ban Regex (push) Has been cancelled Details CI / Compose Bucket Idempotency (push) Has been cancelled Details CI / OCR Service Tests (push) Has been cancelled Details Closes #508. Our gitea-runner advertises labels ubuntu-latest / ubuntu-24.04 / ubuntu-22.04. `runs-on: self-hosted` never matches → dispatched deploy jobs sit in the queue forever. The runner is still genuinely self-hosted (DooD socket, joined to gitea_gitea net, single-tenant per ADR-011) — the `self-hosted` token was just an unconfirmed assumption about the label name. Unblocks #497 / #499 first deploy. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>	2026-05-11 16:15:53 +02:00