Use dedicated PAT for registry login in Gitea Actions workflow
All checks were successful
Build and Push Docker Images / build-and-push (push) Successful in 1m32s
All checks were successful
Build and Push Docker Images / build-and-push (push) Successful in 1m32s
The built-in actions token lacks package registry write scope, causing docker login to fail with "unauthorized". A PAT with write:package scope must be added as the REGISTRY_TOKEN secret. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
@@ -23,7 +23,7 @@ jobs:
|
|||||||
with:
|
with:
|
||||||
registry: ${{ env.REGISTRY }}
|
registry: ${{ env.REGISTRY }}
|
||||||
username: ${{ gitea.actor }}
|
username: ${{ gitea.actor }}
|
||||||
password: ${{ secrets.GITHUB_TOKEN }}
|
password: ${{ secrets.REGISTRY_TOKEN }}
|
||||||
|
|
||||||
- name: Build and push Backend
|
- name: Build and push Backend
|
||||||
uses: docker/build-push-action@v5
|
uses: docker/build-push-action@v5
|
||||||
|
|||||||
Reference in New Issue
Block a user