--pre-release does not work when using custom configuration about versionize

[cabauman]

Hey @LouisRoselli, thanks for reporting. We'll look into a fix.

[LouisRoselli]

@cabauman, I appreciate the fast turn around on this, but the issue is still not fixed.

When running the following commands, I still get the same error in versionize 1.19.1:

versionize --ignore-insignificant-commits --pre-release "alpha"

OR

versionize --pre-release "alpha"

Result:

Semantic versioning conflict: the next version 1.0.0-alpha.0 would be lower than the current version 1.0.0. This can be caused by using a wrong pre-release label or release as version

See this sample repo as example: https://github.com/LouisRoselli/Versionize-Test

[cabauman]

Alright, I'll take another look. The snippet that uses ignore-insignificant-commits is expected to fail, but not the other one.

[cabauman]

There are no tags in the repo you shared but I assume you have a v1.0.0 tag locally on that release commit?

[LouisRoselli]

@cabauman sorry about that. I pushed the tags, and yes it's v1.0.0

[cabauman]

Well, that's odd. I got the correct result.

[LouisRoselli]

@cabauman I figured it out. A total rookie mistake on my part. It turns out I had Versionize installed globally with the --global option in "dotnet tools", and also locally by specifying it in the manifest file in the repo. The local version was on the newest, but the global installed on my machine was on an older version.

Sorry for the confusion, but this is working as expected. Thank You!!!!

[cabauman]

Awesome! Thanks again for the bug report and the update. We didn't have a test case for that scenario, but we do now.