You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: BREAKING_CHANGES.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,6 +40,7 @@
40
40
* Default `RegularExpression` for feature branches is changed from `^features?[/-]` to `^features?[/-](?<BranchName>.+)` to support using `{BranchName}` out-of-the-box
41
41
* Default `RegularExpression` for unknown branches is changed from `.*` to `(?<BranchName>.+)` to support using `{BranchName}` out-of-the-box
42
42
* The `Mainline` mode and the related implementation has been removed completely. The new `TrunkBased` version strategy should be used instead.
43
+
* The `TrunkBased` workflow doesn't support downgrading the increment for calculating the next version. This is the case if e.g. a bump messages has been defined which is lower than the branch increment.
43
44
* The branch related property `is-mainline` in the configuration system has been renamed to `is-main-branch`
44
45
* The versioning mode has been renamed to deployment mode and consists of following values:
* On the `develop`, `release` and `hotfix` branch the introduced branch related property `prevent-increment-when-current-commit-tagged` has been set to `false` to get the incremented instead of the tagged semantic version.
57
+
* On the `develop`, `release` and `hotfix` branch the introduced branch related property `prevent-increment.when-current-commit-tagged` has been set to `false` to get the incremented instead of the tagged semantic version.
and [tracks-release-branches](#tracks-release-branches).
489
+
for [increment](#increment) or other branch related properties.
473
490
474
491
### tag-prefix
475
492
@@ -791,7 +808,9 @@ Another example: branch `features/sc-12345/some-description` would become a pre-
791
808
792
809
Same as for the [global configuration, explained above](#increment).
793
810
794
-
### prevent-increment-of-merged-branch-version
811
+
### prevent-increment-of-merged-branch
812
+
813
+
The increment of the branch merged to will be ignored, regardless of whether the merged branch has a version number or not, when this branch related property is set to true on the target branch.
795
814
796
815
When `release-2.0.0` is merged into main, we want main to build `2.0.0`. If
797
816
`release-2.0.0`is merged into develop we want it to build `2.1.0`, this option
@@ -802,6 +821,10 @@ In a GitFlow-based repository, setting this option can have implications on the
802
821
better version source proposed by the `MergeMessageBaseVersionStrategy`. For
803
822
more details and an in-depth analysis, please see [the discussion][2506].
804
823
824
+
### prevent-increment-when-branch-merged
825
+
826
+
The increment of the merged branch will be ignored when this branch related property is set to `true` on the source branch.
827
+
805
828
### prevent-increment-when-current-commit-tagged
806
829
807
830
This branch related property controls the behvior whether to use the tagged (value set to true) or the incremented (value set to false) semantic version. Defaults to true.
Copy file name to clipboardExpand all lines: src/GitVersion.Configuration.Tests/Configuration/ConfigurationProviderTests.CanWriteOutEffectiveConfiguration.approved.txt
[JsonPropertyDescription("This branch related property controls the behvior whether to use the tagged (value set to true) or the incremented (value set to false) semantic version. Defaults to true.")]
[JsonPropertyDescription($"The regular expression pattern to use to extract the number from the branch name. Defaults to '{ConfigurationConstants.DefaultLabelNumberPattern}'.")]
@@ -91,10 +90,12 @@ public virtual IBranchConfiguration Inherit(IBranchConfiguration configuration)
0 commit comments