Conversation
|
@chwebdude - new PR including the changes to support authentication for NuGet feeds / I think we'll have to improve the pipeline to not break with the versioning - I've removed the assigning of the current BuildNumber to the version for now just to see if the pipeline passes - Maybe only updating the patch number with a given Build Number is the better solution and we're taking the rest from the AssemblyInfo? |
…e latest version once it's on the marketplace.
|
@nilsatomada Thanks for your contribution! But you don't need to touch the version information at all. Therefore, can you update your PR so that there are no versioning changes? |
|
@chwebdude done 👍 - thank you for considering it! |
|
Hey @chwebdude - I think we'll have to change the way on how the version is being created in the pipeline - with the current BuildId we won't be able to update the AssemblyInfo.cs / do you want me to look into that? |
Yes, I thought I already changed that by bypassing that with the If you have time, feel free to have a look into it. I'm quite busy this week, otherwise I will look into it next week. |
adding the support for NuGet Authentication.
Authentication is configured through the following environment variables: