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
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,7 @@
1
+
## v6.1.0
2
+
3
+
* The configuration property `label-number-pattern` was removed. The functionality can be still used by changing the label and the branch name regular expression for pull-request branches.
4
+
1
5
## v6.0.0
2
6
3
7
### Platforms
@@ -60,7 +64,7 @@
60
64
* The `useBranchName` magic string has been removed. Instead use `{BranchName}` for `label`.
61
65
62
66
* The `BranchPrefixToTrim` configuration property has been removed. `RegularExpression` is now used to capture named groups instead.
63
-
* Default `RegularExpression` for feature branches is changed from `^features?[/-]` to `^features?[/-](?<BranchName>.+)` to support using `{BranchName}` out-of-the-box
67
+
* Default `RegularExpression` for feature branches is changed from `^features?[\/-]` to `^features?[\/-](?<BranchName>.+)` to support using `{BranchName}` out-of-the-box
64
68
* Default `RegularExpression` for unknown branches is changed from `.*` to `(?<BranchName>.+)` to support using `{BranchName}` out-of-the-box
65
69
66
70
* The `Mainline` mode and the related implementation has been removed completely. The new `Mainline` version strategy should be used instead.
@@ -840,9 +836,9 @@ The pre-release label to use for this branch. Use the value `{BranchName}` as a
840
836
insert the value of the named group `BranchName` from the [regular expression](#regex).
841
837
842
838
For example: branch `feature/foo` would become a pre-release label
843
-
of `alpha.foo` with `label: 'alpha.{BranchName}'` and `regex: '^features?[/-](?<BranchName>.+)'`.
839
+
of `alpha.foo` with `label: 'alpha.{BranchName}'` and `regex: '^features?[\/-](?<BranchName>.+)'`.
844
840
845
-
Another example: branch `features/sc-12345/some-description` would become a pre-release label of `sc-12345` with `label: '{StoryNo}'` and `regex: '^features?[/-](?<StoryNo>sc-\d+)[-/].+'`.
841
+
Another example: branch `features/sc-12345/some-description` would become a pre-release label of `sc-12345` with `label: '{StoryNo}'` and `regex: '^features?[\/-](?<StoryNo>sc-\d+)[-/].+'`.
846
842
847
843
**Note:** To clear a default use an empty string: `label: ''`
848
844
@@ -871,30 +867,6 @@ The increment of the merged branch will be ignored when this branch related prop
871
867
872
868
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.
873
869
874
-
### label-number-pattern
875
-
876
-
Pull requests require us to extract the pre-release number out of the branch
877
-
name so `refs/pulls/534/merge` builds as `PullRequest.534`. This is a regex with
878
-
a named capture group called `number`.
879
-
880
-
If the branch `mode` is set to `ContinuousDeployment`, then the extracted
881
-
`number`is appended to the name of the pre-release label and the number portion
882
-
is the number of commits since the last label. This enables consecutive commits to
883
-
the pull request branch to generate unique full semantic version numbers when
884
-
the branch is configured to use ContinuousDeployment mode.
885
-
886
-
**Example usage:**
887
-
888
-
```yaml
889
-
branches:
890
-
pull-request:
891
-
mode: ContinuousDeployment
892
-
label: PullRequest
893
-
increment: Inherit
894
-
track-merge-target: true
895
-
label-number-pattern: '[/-](?<number>\d+)[-/]'
896
-
```
897
-
898
870
### track-merge-target
899
871
900
872
Strategy which will look for tagged merge commits directly off the current
0 commit comments