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
_=string.IsNullOrEmpty(selectedCandidate.Tag)&&log.IsInfoEnabled&&log.Info($"No commit found with a valid SemVer 2.0 version{(string.IsNullOrEmpty(tagPrefix)?"":$" prefixed with '{tagPrefix}'")}. Using default version {selectedCandidate.Version}.");
Assert.Contains(logger.Messages, message =>message.Text.Contains($"The calculated version {actualVersion} satisfies the minimum major minor {major}.{minor}.",StringComparison.Ordinal));
47
-
}
44
+
Assert.Contains(logger.Messages, message =>message.Text.Contains($"Ignoring minimum major minor {major}.{minor} because the commit is tagged.",StringComparison.Ordinal));
Copy file name to clipboardExpand all lines: README.md
+2Lines changed: 2 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -206,6 +206,8 @@ Note that `MinVerMinimumMajorMinor` will be redundant after you create the first
206
206
207
207
Also note that if the latest version tag found in the commit history has a higher `MAJOR.MINOR` than `MinVerMinimumMajorMinor`, then `MinVerMinimumMajorMinor` will be ignored.
208
208
209
+
Lastly, if the the current commit has a version tag, the tag will be used as-is, even if it has a lower `MAJOR.MINOR` than `MinVerMinimumMajorMinor`.
210
+
209
211
### Can I use my own pre-release versioning scheme?
210
212
211
213
Yes! MinVer doesn't care what your pre-release versioning scheme is. The default pre-release identifiers are `alpha.0`, but you can use whatever you like in your tags. If your versioning scheme is valid [SemVer 2.x](https://semver.org/spec/v2.0.0.html), it will work with MinVer.
0 commit comments