Repository navigation
ci: fail clearly when the release deploy key is missing - #100
Merged
Merged
Conversation
With no RELEASE_DEPLOY_KEY secret, actions/checkout quietly falls back to the read-only workflow token. A dry run then passed, and a real run only failed at the very end of the push job with a bare 403 (seen on the first run after #97 merged). The push job now starts by failing if the secret is empty, and asserts that checkout used an SSH remote. push-release.sh turns a rejected push into a message that names the likely causes: a missing or read-only deploy key, or rulesets that deploy keys cannot bypass. RELEASING.md describes what a green dry run does and does not prove, and lists the three failure messages. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
plumppig
requested review from
k4paul,
seunghankm and
th3uiguy
as code owners
October 10, 2026 05:40
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.
With no RELEASE_DEPLOY_KEY secret, actions/checkout quietly falls back to the read-only workflow token. A dry run then passed, and a real run only failed at the very end of the push job with a bare 403 (seen on the first run after #97 merged).
The push job now starts by failing if the secret is empty, and asserts that checkout used an SSH remote. push-release.sh turns a rejected push into a message that names the likely causes: a missing or read-only deploy key, or rulesets that deploy keys cannot bypass. RELEASING.md describes what a green dry run does and does not prove, and lists the three failure messages.