Hartmut
69c52e2875
CI / Architecture Guardrails (push) Successful in 3m15s
CI / Typecheck (push) Successful in 4m15s
CI / Assistant Split Regression (push) Successful in 5m0s
CI / Lint (push) Successful in 5m4s
CI / Build (push) Failing after 1m41s
CI / E2E Tests (push) Has been skipped
CI / Fresh-Linux Docker Deploy (push) Has been skipped
CI / Release Images (push) Has been cancelled
CI / Unit Tests (push) Has been cancelled
The release-images job failed on every run because GHCR_USERNAME and
GHCR_TOKEN are not configured on the Gitea repo — and they don't need
to be: Gitea has its own container registry at the same host, reachable
with the auto-provisioned GITHUB_TOKEN.
- Derive the registry host from GITHUB_SERVER_URL (the Gitea base URL)
- Log in with $GITHUB_TOKEN + ${{ github.actor }}
- Tag images as <gitea-host>/<owner>/<repo>-{app,migrator}:sha-<commit>
- Add packages: write permission
- Drop the workflow_call secrets block — no external secrets needed
Consumers (deploy-staging.yml, deploy-prod.yml) that previously pulled
from ghcr.io/<owner>/<repo>-app will need to be updated to pull from
the Gitea registry next; flagging separately.