fix(ci): switch release checkout from SSH key to PAT#1621
Merged
Conversation
The BOT_SSH_KEY deploy key was revoked, breaking the release workflow. Use the existing RELEASE_TOKEN PAT for checkout instead, matching the approach used by other projects. 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.
Summary
ssh-key: ${{ secrets.BOT_SSH_KEY }}withtoken: ${{ secrets.RELEASE_TOKEN }}in the release workflow checkout stepPermission denied (publickey)RELEASE_TOKENPAT is already configured and used later in the workflow forGITHUB_TOKEN, so no new secrets are neededContext
Test plan
RELEASE_TOKENsecret hascontents: writepermission on this repo🤖 Generated with Claude Code