Restrict publish release build to 1.7.2 on master-1.7.x branch #3202
+2
−2
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
paul-dingemans
added a commit
that referenced
this pull request
Dec 16, 2025
* Revert "Master 1.7.x release on master (#3203)" This reverts commit 33aef59. * Revert "Restrict publish release build to 1.7.2 on master-1.7.x branch (#3202)" This reverts commit 9b296ea. * Revert "Temporarily change publish release build flow to release version 1.7.2 while 1.8.0 is already released. (#3201)" This reverts commit 2eea5c5. * Document how to release a patch version on an older minor release
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.
Description
Restrict workflow on master branch to release version 1.7.2 from branch
master-1.7.xChecklist
Before submitting the PR, please check following (checks which are not relevant may be ignored):
Closes #<xxx>orFixes #<xxx>(replace<xxx>with issue number)Documentation is updated. See difference between snapshot and release documentation