Reputation: 33
I have a build pipeline set up on Azure Devops for building a Nuget Package.
So far I have been using only the master branch, after each push to the master branch and then manually triggering the build, the build number got correctly incremented.
Yesterday I decided to create a feature branch, implemented some changes and created a PR. After it got approved and merged into master I manually trigger a new build but this time the build version contains the '-pullrequest1089-0002' string as well. This means that this new version is not available in NuGet package manager for me to install.
I need to somehow configure this so this won't get appended.
This is how my gitversion.yml file looks like:
mode: MainLine
next-version: 1.0.0
Upvotes: 0
Views: 209
Reputation: 33
Thank you all for trying to help. I was not allowed to use pre-release packages. My issue turned out to be rooted in not having enabled CI/CD.
After I turned that option on, it's working correctly.
Upvotes: 1
Reputation: 19451
For this issue , agree with rbennett485 , since the format 1.0.32-xxx
is the format of pre-release nuget packages. To get it to display in nuget package manager, you just need to enable the Include prerelease checkbox.
You can compare the two pictures below to see the difference:
Upvotes: 1