ci: use GH_RELEASE_TOKEN so release tag triggers publish - #7
Merged
Conversation
Tags/releases created with the default GITHUB_TOKEN don't trigger onTag.yml (GitHub anti-recursion), so npm publish never auto-fires. Use a PAT for checkout push and the release-action instead.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Tags/releases created by `onPushToMain.yml` use the default `GITHUB_TOKEN`. GitHub's anti-recursion rule blocks such tags from triggering other workflows, so `onTag.yml` (`push: tags: v*`) never auto-fires — the tag and release appear, but nothing publishes to npm. Manual dispatch on `main` also fails because the `publish` environment only allows `v*` tag refs.
Fix
Use the `GH_RELEASE_TOKEN` PAT for checkout and the release-action. A tag created by a PAT triggers downstream workflows normally, so `onTag.yml` fires on the `v*` tag and satisfies the environment's tag policy. Fully automatic, no manual dispatch.
Requires
`onTag.yml` unchanged.