release: allow for branch protection in release steps#1767
Merged
github-actions[bot] merged 1 commit intoquay:mainfrom Mar 2, 2026
Merged
release: allow for branch protection in release steps#1767github-actions[bot] merged 1 commit intoquay:mainfrom
github-actions[bot] merged 1 commit intoquay:mainfrom
Conversation
hdonnay
reviewed
Mar 2, 2026
Since the introduction of the branch protection rule to stop users pushing directly to `main` the previous release steps started failing. This changes the instructions to require the user merges the changelog update before tagging the release. Signed-off-by: crozzy <joseph.crosland@gmail.com>
crozzy
force-pushed
the
release-branch-protection
branch
from
7ea7f86 to
46450a7
Compare
Member
|
This could probably be even smarter and use the |
hdonnay
approved these changes
Mar 2, 2026
Contributor
Author
|
/fast-forward |
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
2 participants
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.
Since the introduction of the branch protection rule to stop users pushing directly to
mainthe previous release steps started failing. This changes the instructions to require the user merges the changelog update before tagging the release.