Fix release chain: use App token in release.yml#17
Merged
Conversation
…ease Use GitHub App token instead of GITHUB_TOKEN for gh release create, so the release:published event is not suppressed by GitHub Actions. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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.
Summary
GITHUB_TOKENinrelease.ymlfor thegh release createsteppublish.ymlnever triggering after a release is created, because GitHub Actions suppresses events fromGITHUB_TOKENrelease-version-sync.ymlin commit5d62a41Test plan
masterrelease/*PRrelease.ymlcreates the GitHub releasepublish.ymlis triggered by therelease: [published]event and publishes to npm🤖 Generated with Claude Code