Skip to content

fix(ci): use GITHUB_TOKEN for GHCR authentication#1577

Merged
fclairamb merged 1 commit intomainfrom
fix/docker-ghcr-auth
Jan 11, 2026
Merged

fix(ci): use GITHUB_TOKEN for GHCR authentication#1577
fclairamb merged 1 commit intomainfrom
fix/docker-ghcr-auth

Conversation

@fclairamb
Copy link
Owner

Summary

  • Replace CR_PAT with GITHUB_TOKEN for GitHub Container Registry authentication
  • Add permissions block with packages:write and contents:read
  • Fix "denied: denied" error in Docker workflow

Root Cause

The workflow was using secrets.CR_PAT (a personal access token) for GHCR authentication, which was either expired, revoked, or not configured.

Solution

Use the built-in GITHUB_TOKEN which is automatically provided by GitHub Actions and doesn't require manual secret management.

Test plan

  • Merge this PR
  • Create a new tag (v0.15.1) to trigger the Docker workflow
  • Verify the Docker images are pushed successfully to GHCR

🤖 Generated with Claude Code

Replace CR_PAT with GITHUB_TOKEN for GitHub Container Registry
authentication. The personal access token was causing "denied" errors.

- Add permissions block with packages:write and contents:read
- Use secrets.GITHUB_TOKEN instead of secrets.CR_PAT
- Use github.actor for username (recommended for GITHUB_TOKEN)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@fclairamb fclairamb merged commit 2ff5e33 into main Jan 11, 2026
4 checks passed
@fclairamb fclairamb deleted the fix/docker-ghcr-auth branch January 11, 2026 15:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant