Installing 4.3.0 with Nuke build causes multiple versions to be referenced #985
Closed
jamesshenry
started this conversation in
General
Replies: 2 comments
-
|
Why do you feel this is MinVer specific? |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
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. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
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.0in a repository with a build projectSteps to reproduce the behaviour:
dotnet tool install nuke.globaltool --globalnukeand setup build projectnuke :add-package minver-cli --version 4.3.0in repositorynuke PrintExpected behaviour
Should receive output similar to in 4.2.0:
Actual behaviour
Workarounds
Reverting back to 4.2.0 resolves the issue
Beta Was this translation helpful? Give feedback.
All reactions