Repository navigation
ci: push the release over SSH with a deploy key - #64
Merged
Merged
Conversation
A required-checks ruleset on main rejects a release commit pushed with the job token or an app token, and neither can be a bypass actor. The release job now provisions a deploy key from the release environment, points origin at the SSH URL so semantic-release pushes with it, and removes the key afterwards, as combinatrix, claude-code-action and dependency-heal do.
Mearman
enabled auto-merge (rebase)
October 31, 2026 11:14
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 security review couldn’t start because the paying account has exhausted its Codex allowance and has insufficient available credits. The payer can check their balance and add credits in the Codex usage dashboard, then try again. If you do not manage the paying account, contact this repository's admins. |
|
🎉 This PR is included in version 0.8.3 🎉 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
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.
A required-checks ruleset on
mainrejects a release commit pushed with the job token or an app token, and neither can be a bypass actor. The release job now provisions a write deploy key from thereleaseenvironment (limited to main), pointsoriginat the SSH URL so semantic-release pushes with it, and removes the key afterwards, as combinatrix, claude-code-action and dependency-heal do. The key and the ruleset's DeployKey bypass are already in place. The pull request's merge is the first release through it.The release step passes
--repository-urlwith the SSH URL, because semantic-release pushes to itsrepositoryUrl(by defaultpackage.json's httpsrepositoryfield), not toorigin.