Closed henry-js closed 4 months ago
Why do you feel this is MinVer specific? Have you looked at the package difference in NuGet Package explorer (I'd be surprised if there were any structural changes)
Nuke seems to be the major moving part here, and I'm not yet convinced this is a bug in MinVer. Moving to a discussion for now. If it is proven that there is a bug in MinVer then we can address it.
Version(s)
4.3.0 The version(s) in which you have observed the bug.
To reproduce
Run
nuke :add-package minver-cli --version 4.3.0
in a repository with a build project Steps to reproduce the behaviour:Create repository with a console app in src
Install nuke global tool
dotnet tool install nuke.globaltool --global
Run
nuke
and setup build projectRun
nuke :add-package minver-cli --version 4.3.0
in repositoryAdd Print target that should print minver semantic version
Run
nuke Print
Expected behaviour
Should receive output similar to in 4.2.0:
Actual behaviour
Workarounds
Reverting back to 4.2.0 resolves the issue