Skip to content

ci(release): push release tag with KIT_RELEASE_TOKEN so the release pipeline fires #51

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
BCook98 merged 1 commit into from
Jun 17, 2026
Merged

ci(release): push release tag with KIT_RELEASE_TOKEN so the release pipeline fires #51

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
9 changes: 8 additions & 1 deletion .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,14 @@ jobs:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
with: { fetch-depth: 0 }
# The tag push in scripts/tag-release.sh must use a PAT, not the
# default GITHUB_TOKEN: GitHub does NOT fire workflow triggers for tags
# pushed with GITHUB_TOKEN, so the downstream GoReleaser/Homebrew/notify
# pipeline would silently never run. Persisting the PAT here makes the
# `git push origin "${TAG}"` use it.
with:
fetch-depth: 0
token: ${{ secrets.KIT_RELEASE_TOKEN }}
- uses: actions/setup-node@v4
with: { node-version: 22 }
- run: npm ci
Expand Down
Loading