Skip to content

fix(release): trigger release-cli via KIT_RELEASE_TOKEN tag push + manual dispatch#48

Merged
BCook98 merged 1 commit into
mainfrom
fix-release-trigger
Jun 16, 2026
Merged

fix(release): trigger release-cli via KIT_RELEASE_TOKEN tag push + manual dispatch#48
BCook98 merged 1 commit into
mainfrom
fix-release-trigger

Conversation

@BCook98

@BCook98 BCook98 commented Jun 16, 2026

Copy link
Copy Markdown
Contributor

The changesets publish step pushes the `vX.Y.Z` tag with `GITHUB_TOKEN`, but the fallback secret was `RELEASE_PAT` — a tag pushed with the default `GITHUB_TOKEN` (or a non-PAT) does not trigger tag-listening workflows, so `release-cli.yml` never fired. This wires the real PAT and makes the CLI release re-runnable by hand.

  • release.yml: token fallback `RELEASE_PAT` -> `KIT_RELEASE_TOKEN` (a real PAT push triggers the tag workflow).
  • release-cli.yml: add `workflow_dispatch` (input `tag`); checkout uses `ref: ${{ github.event.inputs.tag || github.ref_name }}` so a manual run builds the chosen tag; the `notify-consumers` dispatch sends `${{ github.event.inputs.tag || github.ref_name }}` so the dispatched version is the TAG, not a branch, on manual runs.

actionlint: clean on both files.

…nual dispatch

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@BCook98
BCook98 merged commit 0e71f3f into main Jun 16, 2026
6 checks passed
@BCook98
BCook98 deleted the fix-release-trigger branch June 16, 2026 10:50
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