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
+13Lines changed: 13 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -71,6 +71,19 @@
71
71
* When creating a branch with name `hotfix/next` (by using the `GitFlow` workflow) or `release/next` (by the `GitHubFlow` workflow) the resulting version will yield to a patched version per default.
72
72
* If you have a tag `1.0.0` on `main` and branch from `main` to `release/1.0.1` then the next version number will be `1.1.0` when using the `GitFlow` workflow. This behavior is expected (but different compared to the `GitHubFlow` workflow) because on the `GitFlow` workflow you have an addition branch configuration with name hotfix where `is-release-branch` is set to `true`. That means if you want `1.0.1` as a next version you need to branch to `hotfix/1.0.1` or `hotfix/next`. On the other hand if you use the `GitHubFlow` workflow the next version number will be `1.0.1` because the increment on the `release` branch is set to `Patch`.
73
73
74
+
### Legacy Output Variables
75
+
76
+
The following legacy output variables have been removed in this version:
77
+
78
+
* `BuildMetaDataPadded`
79
+
* `LegacySemVer`
80
+
* `LegacySemVerPadded`
81
+
* `NuGetVersionV2`
82
+
* `NuGetVersion`
83
+
* `NuGetPreReleaseTagV2`
84
+
* `NuGetPreReleaseTag`
85
+
* `CommitsSinceVersionSourcePadded`
86
+
74
87
## v5.0.0
75
88
76
89
* Version numbers in branches other than `release` branches are no longer
0 commit comments