ci(release): drop broken SSH deploy key, use GITHUB_TOKEN#120
Merged
antosubash merged 1 commit intomainfrom Apr 23, 2026
Merged
ci(release): drop broken SSH deploy key, use GITHUB_TOKEN#120antosubash merged 1 commit intomainfrom
antosubash merged 1 commit intomainfrom
Conversation
The checkout step passed ssh-key: ${{ secrets.DEPLOY_KEY }}, but the
secret's contents are no longer a valid OpenSSH private key, causing
every release run to fail at checkout with "error in libcrypto" and
"Permission denied (publickey)".
The job already declares contents: write, so GITHUB_TOKEN has the
permission it needs to push the version bump and tag. Remove the
ssh-key input and rely on persist-credentials so the default token
handles the push.
Deploying simplemodule-website with
|
| Latest commit: |
dbffe28
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://d9c73fb5.simplemodule-website.pages.dev |
| Branch Preview URL: | https://feature-jovial-khorana-8bb24.simplemodule-website.pages.dev |
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.DEPLOY_KEY }}from the release workflow's checkout step and rely onGITHUB_TOKENviapersist-credentials: true.Why
Every run of
release.ymlcurrently fails at the very first step:The
DEPLOY_KEYsecret is no longer a parseable OpenSSH private key (likely CRLF corruption or a stale value), soactions/checkout@v6can't authenticate over SSH.The job already declares
permissions: contents: write, which grants the defaultGITHUB_TOKENenough authority to push the version bump commit and tag back to `main`. Dropping the SSH input unblocks the workflow without adding new secrets.Reviewer notes / caveats
Test plan