fix(release): authenticate pushes with deploy key - #78
Merged
Conversation
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.
Summary
Authenticate the release workflow鈥檚 atomic
mainand tag push with the repository-scoped release deploy key. Keep the default GitHub Actions token for GitHub Release publication.Motivation
The repository ruleset rejects direct pushes made with the default
GITHUB_TOKEN, even after every release build and required check succeeds. The write-enabled deploy key is the dedicated ruleset bypass actor for release ref publication.Technical details
The publish checkout configures
RELEASE_DEPLOY_KEYas its SSH credential, which remains available to the existing leased atomic push and is removed by the checkout post-step. The release guide records the deploy-key, ruleset, and Actions-secret requirements.