Repository navigation
ci: push the release commit and tags with a deploy key - #14
Merged
Merged
Conversation
GITHUB_TOKEN cannot bypass the main ruleset, so the release job now pushes with the repository deploy key over SSH. Checkout no longer persists a credential, the key is written to the runner's temporary directory in the step before the release and removed afterwards, and the release step rewrites https GitHub URLs to SSH through git's per-process config so the orchestrator's plain `git push origin` authenticates with the key. GITHUB_TOKEN stays in that step for the GitHub API.
State that the release commit and tags reach the protected main through a deploy key listed as a bypass actor on the ruleset, and what GITHUB_TOKEN is still used for.
Mearman
marked this pull request as ready for review
October 10, 2026 11:27
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 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
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.
The release job now pushes its release commit and tags to the protected
mainwith the repository deploy key over SSH, as json-compose does, instead of withGITHUB_TOKEN.The orchestrator pushes with
git push --atomic origin HEAD:<branch> <tags>(semantic-release-workspacesrc/git.ts,pushHeadAndTags) and has norepositoryUrloption, so the key is wired in at the step: checkout no longer persists a credential, the key is written to$RUNNER_TEMPfrom step env in the step before Release, and the Release step setsGIT_SSH_COMMANDplus a per-processurl.git@github.com:.insteadOfrewrite sooriginresolves to SSH.GITHUB_TOKENstays in that step for@semantic-release/github, which only calls the API. The key is removed in analways()step.README and CONTRIBUTING state the mechanism. The first real push happens on the next release run; the
mainruleset must list the deploy key as a bypass actor before then.