Skip to content

CI: use GITHUB_TOKEN instead of the expired TOKEN secret - #2

Merged
deven1003 merged 1 commit into
mainfrom
ci/use-github-token
Oct 11, 2026
Merged

deven1003 merged 1 commit into
mainfrom
ci/use-github-token

Conversation

@deven1003

Copy link
Copy Markdown
Owner

The TOKEN personal access token secret (created 2025-08-03) is no longer valid. After #1 was merged, the push to main failed at Login to GitHub Container Registry with denied: denied.

This switches the workflow to the built-in GITHUB_TOKEN, so nothing needs to be rotated:

  • docker job: permissions: packages: write (plus contents: read), and logs in to GHCR with secrets.GITHUB_TOKEN.
  • update-k8s job: permissions: contents: write, and checkout uses the default token, which lets it commit the updated kubernetes/deployment.yaml back to main.

This matches .github/workflows/README.md, which already lists GITHUB_TOKEN as the only required secret. Once this is merged, the TOKEN secret can be deleted.

Note: PR runs skip the login and push steps, so the registry push is only exercised on the first push to main after merge.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@deven1003
deven1003 merged commit 8d674f6 into main Oct 11, 2026
5 checks passed
@deven1003
deven1003 deleted the ci/use-github-token branch October 11, 2026 19:36
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