Fix creating minor release if new major release branch already exist#282
Merged
Ocramius merged 1 commit intolaminas:1.26.xfrom Feb 17, 2026
Conversation
…nch exist. This is useful if a new major release is already in the work but new feature are still coming into the current latest major. The case is as follows: When we already have these branches: 1.0.x, 1.1.x, 1.2.x, 2.0.x And we release 1.2.0, then we expect that 1.3.x is created and set as a new default branch. Signed-off-by: Daniel Badura <daniel.badura@patchlevel.de>
DanielBadura
force-pushed
the
fix-creating-new-minor-branch-if-new-major-exist
branch
from
d9cc049 to
f3687c5
Compare
Member
|
For our purposes new minor branch needs to be created only if |
Contributor
Author
|
So is this a rule you want to enforce here? This also aligns with our purpose so I'm fine with that. |
Ocramius
approved these changes
Feb 17, 2026
Member
Ocramius
left a comment
Ocramius
left a comment
There was a problem hiding this comment.
Let's give this a shot, thanks @DanielBadura!
DanielBadura
deleted the
fix-creating-new-minor-branch-if-new-major-exist
branch
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
4 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.
This patch fixes the minor branch creation if already a new major branch exist. This is useful if a new major release is already in the work but new feature are still coming into the current latest major.
The case is as follows:
When we already have these branches: 1.0.x, 1.1.x, 1.2.x, 2.0.x And we release 1.2.0, then we expect that 1.3.x is created and set as a new default branch.