fix: use PAT for release-please workflow#35
Merged
jeff-atriumn merged 1 commit intomainfrom Feb 26, 2026
Merged
Conversation
GITHUB_TOKEN cannot create PRs due to enterprise-level workflow permission restrictions. Use a fine-grained PAT instead. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Change Summary
Switch release-please workflow from
GITHUB_TOKENtoRELEASE_PLEASE_TOKEN(fine-grained PAT). The enterprise-level policy disables write permissions forGITHUB_TOKEN, preventing release-please from creating PRs.Risk & Impact Assessment
Risk Level: low
Test Plan
RELEASE_PLEASE_TOKENsecret is set on the repoManual Verification Steps
🤖 Generated with Claude Code