ci(release): use REGISTRY_TOKEN PAT for Gitea registry login
CI / Architecture Guardrails (push) Successful in 3m3s
CI / Lint (push) Successful in 3m49s
CI / Typecheck (push) Successful in 3m56s
CI / Assistant Split Regression (push) Successful in 5m54s
CI / Build (push) Successful in 6m48s
CI / E2E Tests (push) Successful in 5m23s
CI / Fresh-Linux Docker Deploy (push) Successful in 6m10s
CI / Release Images (push) Failing after 2m7s
CI / Unit Tests (push) Successful in 7m22s

The auto-provisioned GITHUB_TOKEN in Gitea Actions does not carry
package-registry write permission. Use a personal access token stored
as a repo secret instead.
This commit is contained in:
2026-04-13 08:09:56 +02:00
parent 62de038497
commit 69d74881dc
+1 -1
View File
@@ -46,7 +46,7 @@ jobs:
# GITHUB_TOKEN is auto-provisioned by Gitea Actions for the running
# workflow; no manual secret configuration required.
run: |
echo "${{ secrets.GITHUB_TOKEN }}" | \
echo "${{ secrets.REGISTRY_TOKEN }}" | \
docker login "${{ steps.registry.outputs.host }}" \
-u "${{ github.actor }}" --password-stdin