From 4b7c158eac500ae5111f3e722915fb5412cdbac2 Mon Sep 17 00:00:00 2001 From: aayalew Date: Fri, 10 Jul 2026 17:52:26 +0300 Subject: [PATCH] fix(demo): use REGISTRY_TOKEN for Gitea package registry login GITHUB_TOKEN cannot auth to /v2/; PAT with write:package is required. Co-authored-by: Cursor --- .gitea/workflows/build.yaml | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/.gitea/workflows/build.yaml b/.gitea/workflows/build.yaml index af85cd6..9bdf816 100644 --- a/.gitea/workflows/build.yaml +++ b/.gitea/workflows/build.yaml @@ -20,12 +20,14 @@ jobs: id: meta run: echo "tag=${GITHUB_SHA::8}" >> "$GITHUB_OUTPUT" + # GITHUB_TOKEN cannot authenticate to Gitea's /v2/ registry; use a PAT + # with write:package stored as repo secret REGISTRY_TOKEN. - name: Login to Gitea container registry uses: docker/login-action@v3 with: registry: ${{ env.REGISTRY }} - username: ${{ github.actor }} - password: ${{ secrets.GITHUB_TOKEN }} + username: ${{ github.repository_owner }} + password: ${{ secrets.REGISTRY_TOKEN }} - name: Build and push uses: docker/build-push-action@v6