Skip to content

ci: tag with the built-in GITHUB_TOKEN instead of S9_GITHUB_TOKEN #142

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
MusaMisto merged 1 commit into from
Sep 29, 2026
Merged

ci: tag with the built-in GITHUB_TOKEN instead of S9_GITHUB_TOKEN #142

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions .github/workflows/ci-cd.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -78,9 +78,9 @@ jobs:
# Gateway-API cluster kubeconfig (V2)
kubeconfig-gateway: ${{ secrets.S9DEV_KUBECONFIG_V2 }}

# Custom PAT used for git tagging only (the GHCR chart push/pull use the
# built-in GITHUB_TOKEN, so this PAT does not need write:packages).
github-token: ${{ secrets.S9_GITHUB_TOKEN }}
# Tagging uses the job's built-in GITHUB_TOKEN (contents: write is granted
# above). The org PAT used here before expired (HTTP 401).
github-token: ${{ secrets.GITHUB_TOKEN }}

# App configuration passed to helm --set-string during deploy (masked)
helm-set-secret-values: 'db=${{ secrets.DBCS }}'
Expand Down
Loading