fix(ci): push release commits over SSH using a deploy key - #9
Merged
Conversation
The release job's git push to main was rejected once main's own ruleset started requiring a passing "Required Checks" status on every push, including direct ones -- the default GITHUB_TOKEN has no documented way to bypass a repository ruleset. A write-access deploy key, registered as a DeployKey bypass actor on the ruleset, lets actions/checkout authenticate the push over SSH instead, without introducing a GitHub App installation or an org-admin personal token.
Mearman
force-pushed
the
fix/release-push-via-deploy-key
branch
from
September 12, 2026 12:23
30de3ce to
2922ea7
Compare
Mearman
marked this pull request as ready for review
September 12, 2026 12:25
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
🎉 This PR is included in version 2.11.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
main's own ruleset now requires a passing "Required Checks" status on every push to main, including the release job's own direct push of the version-bump commit and tag. The default GITHUB_TOKEN has no documented way to bypass a repository ruleset (confirmed against GitHub's own docs and community discussions), so that push started failing with GH013 rule violations.
A write-access deploy key (id 163076140, added to this repo) registered as a DeployKey bypass actor on the ruleset lets the release job authenticate its push over SSH instead. The private key is stored as the RELEASE_DEPLOY_KEY repo secret; actions/checkout's ssh-key input wires it in.