From 3485bf08739b3b065e31085ec2a4e5911df7acfc Mon Sep 17 00:00:00 2001 From: Wuesteon Date: Mon, 8 Dec 2025 18:16:11 +0100 Subject: [PATCH] fix(ci): use GITHUB_TOKEN for GHCR auth on staging server MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Match the working pattern from cd-staging.yml instead of requiring a separate GHCR_PAT secret. GITHUB_TOKEN is automatically available in GitHub Actions and has the necessary permissions for ghcr.io. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude --- .github/workflows/cd-staging-tagged.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/cd-staging-tagged.yml b/.github/workflows/cd-staging-tagged.yml index 525a6f023..a77f63f3e 100644 --- a/.github/workflows/cd-staging-tagged.yml +++ b/.github/workflows/cd-staging-tagged.yml @@ -309,7 +309,7 @@ jobs: - name: Login to GHCR on staging server run: | ssh ${{ secrets.STAGING_USER }}@${{ secrets.STAGING_HOST }} << EOF - echo "${{ secrets.GHCR_PAT }}" | docker login ghcr.io -u ${{ github.repository_owner }} --password-stdin + echo "${{ secrets.GITHUB_TOKEN }}" | docker login ghcr.io -u ${{ github.actor }} --password-stdin EOF - name: Deploy service