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
- Integrate the fallback branch configuration with all branch related properties in the root configuration.
- Create a new configuration section with name unknown to ensure the unknown branch configuration.
- The way how the configuration (file, parameter) will be merged with the build-in gitflow configuration has been changed.
Copy file name to clipboardExpand all lines: BREAKING_CHANGES.md
+15-5Lines changed: 15 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,12 +6,22 @@
6
6
* Instead of having a single effective configuration, we now have one effective configuration per branch where the increment strategy is not set to `inherit`.
7
7
* The new implementation of the branch configuration inheritance affects per default only the pull-requests, hotfix and feature branches. In this case the next version will be generated like the child branch is not existing and the commits have been made on the source branch.
8
8
* The following example illustrates this behavior. On the feature branch the semantic version `1.1.0-just-a-test.1+2` will now be generated instead of version `1.0.0-just-a-test.1+3` previously:
9
-
```
9
+
```
10
10
* 1f1cfb4 52 minutes ago (HEAD -> feature/just-a-test)
11
-
* 1f9654d 54 minutes ago (release/1.1.0)
12
-
* be72411 56 minutes ago (develop)
13
-
* 14800ff 58 minutes ago (tag: 1.0.0, main)
14
-
```
11
+
* 1f9654d 54 minutes ago (release/1.1.0)
12
+
* be72411 56 minutes ago (develop)
13
+
* 14800ff 58 minutes ago (tag: 1.0.0, main)
14
+
```
15
+
* A new `unknown` branch magic string has been introduced to give the user the possibility to specify the branch configuration for a branch which is not known. A branch is not known if only the regular expression of the branch configuration with the name `unknown` is matching. Please notice that this branch configuration behaves like any other branch configurations.
16
+
* Additional `fallback` branch configuration properties have been introduced at the root to define base properties which will be inherit to the branch configurations. That means if no other branch configuration in the inheritance line defines the given property the fallback property applies. Notice that the inheritance tree can be controlled using the increment strategy property in the branch configuration section.
17
+
* The following example illustrates this behavior. The hotfix branch configuration overrides the main branch configuration and the result overrides the fallback branch configuration.
18
+
```
19
+
* 1f1cfb4 52 minutes ago (HEAD -> hotfix/just-a-test)
20
+
* 14800ff 58 minutes ago (tag: 1.0.0, main)
21
+
```
22
+
* When overriding the configuration with e.g. GitVersion.yaml the software distinguishes between properties who are not existent and properties who are `null`. This is especially important if the user wants to define branch related configuration which are marked with `increment` strategy `Inherit`.
23
+
* Following root configuration properties have been removed:
ExpectedResult=$"Could not parse /overrideconfig option: assembly-versioning-scheme=WrongEnumValue. Ensure that 'value' is valid for specified 'key' enumeration: {System.Environment.NewLine}"+
0 commit comments