ci: switch back to REGISTRY_TOKEN PAT for registry auth

Even on Gitea 1.26 the auto-token still hits the registry with 401 in this environment. Use the gitea-admin PAT stored as REGISTRY_TOKEN. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-16 21:09:46 -04:00
parent 5c7e4d45d4
commit 48c0351be3
5 changed files with 20 additions and 20 deletions
@@ -59,8 +59,8 @@ jobs:
        uses: docker/login-action@b45d80f862d83dbcd57f89517bcf500b2ab88fb2 # v4.0.0
        with:
          registry: git.farh.net
-          username: ${{ github.actor }}
-          password: ${{ secrets.GITEA_TOKEN }}
+          username: gitea-admin
+          password: ${{ secrets.REGISTRY_TOKEN }}

      - name: Build and push worker image
        uses: docker/build-push-action@d08e5c354a6adb9ed34480a06d141179aa583294 # v7.0.0
@@ -91,8 +91,8 @@ jobs:
        uses: docker/login-action@b45d80f862d83dbcd57f89517bcf500b2ab88fb2 # v4.0.0
        with:
          registry: git.farh.net
-          username: ${{ github.actor }}
-          password: ${{ secrets.GITEA_TOKEN }}
+          username: gitea-admin
+          password: ${{ secrets.REGISTRY_TOKEN }}

      - name: Build and push API image
        uses: docker/build-push-action@d08e5c354a6adb9ed34480a06d141179aa583294 # v7.0.0