Repository navigation
ci: push the release over SSH with a deploy key - #7
Merged
Merged
Conversation
The default GITHUB_TOKEN cannot bypass a branch ruleset, so the release commit and tag push needs a bypass identity. The Release job checks out with the RELEASE_DEPLOY_KEY deploy key and release.config.ts uses the SSH repositoryUrl so semantic-release does not embed the token.
Mearman
marked this pull request as ready for review
October 2, 2026 05:13
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 1.1.1 🎉 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.
Switches the release to the deploy-key model eslint-config already uses. The Release job's checkout takes the RELEASE_DEPLOY_KEY secret with persist-credentials true, and release.config.ts sets the SSH repositoryUrl, so semantic-release pushes the release commit and tag over SSH instead of embedding the default token, which cannot bypass the main ruleset. The job stays on a GitHub-hosted runner with id-token: write for npm trusted publishing, and no other job changes.
A ci: commit is a patch release under release.config.ts, so merging triggers the release run that proves the change: with main still unprotected it must push the release commit and tag over SSH and publish with provenance. The ruleset is created afterwards by the owner.