fix: push releases with a deploy key#163
Merged
Merged
Conversation
The main branch ruleset rejects direct pushes from the workflow token, and the GitHub Actions app cannot be added as a bypass actor on this repository. The release workflow now pushes with a deploy key (RELEASE_DEPLOY_KEY secret) that is exempted from the ruleset via a deploy-key bypass. Deploy key pushes also trigger workflows normally, unlike workflow token pushes, so the tag push now starts the ci, npm, and docker publishes by itself and the explicit dispatch step is gone. The workflow_dispatch triggers on those workflows stay for manual recovery.
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.
The main branch ruleset rejects direct pushes from the workflow
token, and the GitHub Actions app cannot be added as a bypass actor
on this repository. The release workflow now pushes with a deploy
key (RELEASE_DEPLOY_KEY secret) that is exempted from the ruleset
via a deploy-key bypass.
Deploy key pushes also trigger workflows normally, unlike workflow
token pushes, so the tag push now starts the ci, npm, and docker
publishes by itself and the explicit dispatch step is gone. The
workflow_dispatch triggers on those workflows stay for manual
recovery.