ci: cut release without opening a PR#88
Merged
Merged
Conversation
GITHUB_TOKEN cannot create PRs unless a separate repo setting is enabled, and the PR path still needs review under the main ruleset. Commit the changelog on main, tag, and publish directly instead. Document the need for a GitHub Actions ruleset bypass (or RELEASE_GITHUB_TOKEN).
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
GitHub Actions is not permitted to create or approve pull requestsmain, tags, pushes both, then publishes (GoReleaser + npm)RELEASE_GITHUB_TOKENRepo setup required for the push
Rulesets → main → Bypass list → add GitHub Actions → Always
(without this, push to
mainwill be rejected the same way PRs were)Test plan
maingh workflow run "Cut Release" -f bump=patch -f dry_run=truegh workflow run "Cut Release" -f bump=patch(or finish v1.2.3 with-f version=1.2.3)