Release workflow: Use PR squash-merge with GITHUB_TOKEN for branch protection compatibility#1491
Open
Release workflow: Use PR squash-merge with GITHUB_TOKEN for branch protection compatibility#1491
Conversation
…fast-forward Co-authored-by: LogFlames <36220731+LogFlames@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix issue #1490
Release workflow: Use PR squash-merge with GITHUB_TOKEN for branch protection compatibility
Feb 7, 2026
Member
|
@algomaster99 for this new workflow, could you enable github actions to create PRs? The option is grayed out for me. Under Actions > General:
|
Member
|
It was greyed out because we control these configuration on a organization level. I enabled in our organization settings. |
algomaster99
approved these changes
Feb 7, 2026
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.
The release workflow attempted to fast-forward merge and push directly to
mainusingJRELEASER_GITHUB_TOKEN, bypassing branch protection rules that require PR approval.Changes
Checkout token: Changed from
JRELEASER_GITHUB_TOKENtoGITHUB_TOKEN(line 42)PR creation: Replaced fast-forward merge + retry push loop with single PR creation step (lines 170-178)
Release version X.Y.Z(wasRelease $BRANCH_NAME ff-merge)GITHUB_TOKENfor API authorizationJRELEASER_GITHUB_TOKEN remains in JReleaser step for Maven Central publishing
The workflow now creates an approvable PR that respects branch protection when squash-merged.
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.