fix: use github.token instead of REPOSITORY_PUSH_TOKEN in release wor…#5
Merged
Conversation
…kflows The PR-based catalog workflow does not need a PAT. The built-in github.token is sufficient since the workflows already declare contents: write and pull-requests: write permissions. Remove explicit token: and GH_TOKEN overrides so that actions/checkout uses the default GITHUB_TOKEN (avoiding failures when REPOSITORY_PUSH_TOKEN is unset or stale in forks), and gh pr create picks up GITHUB_TOKEN automatically. Also drop persist-credentials: false from create-github-prerelease which would have broken git push --follow-tags without a separately configured credential. Co-Authored-By: Claude Sonnet 4.6 (1M context) <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.
…kflows
The PR-based catalog workflow does not need a PAT. The built-in github.token is sufficient since the workflows already declare contents: write and pull-requests: write permissions.
Remove explicit token: and GH_TOKEN overrides so that actions/checkout uses the default GITHUB_TOKEN (avoiding failures when REPOSITORY_PUSH_TOKEN is unset or stale in forks), and gh pr create picks up GITHUB_TOKEN automatically.
Also drop persist-credentials: false from create-github-prerelease which would have broken git push --follow-tags without a separately configured credential.