TeamCity plugin - nuget package version changed (zero added)

• 
  The nuget team forced SemVer as the standard a few years ago, and has no desire to roll it back: https://github.com/NuGet/Home/issues/3050

  Sean_Lively July 10, 2019 00:25

  - 0 +
• 
  Thanks for the issue link SeanL. I can fully understand forcing SemVer on nuget packages if they are intented to land on public nuget feeds, however many companies use internal nuget feeds for deployment pipeline. In that case I think SemVer doesn't need to be forced.
  We package our applications using Octopack (from Octopus Deploy) and we don't have such problem. It seems Octopus Deploy solved that by creating custom nuget build https://github.com/OctopusDeploy/Issues/issues/2898
  
  Piotr

  Baggs July 10, 2019 07:34

  - 0 +
• 
  That's the frustrating thing about the way the Nuget team handled this- it's a subtle problem that will continue to creep through the ecosystem, randomly breaking processes as the tools are updated. I'm sure eventually I'll update my ProGet server to find half of my deployment processes failed due to SemVer normalization.

  Sean_Lively July 10, 2019 15:56

  - 0 +
• 
  Hi Piotr,
  
  Currently we support valid Nuget version formats only.
  
  If you wish to you can post this on the SQL Change Automation forum: https://redgate.uservoice.com/forums/267000-sql-change-automation
  
  That forum is monitored by the Product Management team who use it as an important source when deciding what features to add or enhance in the tool.
  

  Sergio R July 11, 2019 09:39

  - 0 +

Add comment

Please sign in to leave a comment.