ci: use REGISTRY_TOKEN PAT for container registry auth
CI / Type-check & lint (push) Successful in 52s
CI / Build & push worker image (push) Failing after 1m50s
CI / Build & push API image (push) Failing after 1m50s

The auto-provided GITEA_TOKEN doesn't grant write:package scope
in Gitea 1.25 even when permissions.packages: write is declared.
Switch registry logins to a dedicated PAT stored as REGISTRY_TOKEN.
Keep GITEA_TOKEN for semantic-release-gitea API calls.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
2026-05-16 20:35:51 -04:00
parent a6da45f6bf
commit f3d73c9160
5 changed files with 10 additions and 10 deletions
+1 -1
View File
@@ -31,7 +31,7 @@ jobs:
- name: Log in to Gitea OCI registry
run: |
echo "${{ secrets.GITEA_TOKEN }}" | helm registry login git.farh.net \
echo "${{ secrets.REGISTRY_TOKEN }}" | helm registry login git.farh.net \
--username "${{ github.actor }}" \
--password-stdin