InjectModuleInitializer icon indicating copy to clipboard operation
InjectModuleInitializer copied to clipboard
verified publisher icon kzu

SemVer 2.0 issue with InjectModuleinitializer and TFS Package Management Feed

Open realrubberduckdev opened this issue 7 years ago • 1 comments

Nuget cannot push InjectModuleInitializer 2.0.0 to TFS Nuget Package Management Feed with the error:

Response status code does not indicate success: 400 (Bad Request - The package is invalid: The package version had build metadata. We do not support versions with build metadata (TFS Activity ID: 04DB34C2-BF4E-4E94-930B-E874CB6154A6)).

  • Is there a reason the version number has metadata information?
  • Is there any workaround until TFS allows semver 2.0 versioned packages?

Thanks.

realrubberduckdev avatar Oct 22 '18 13:10 realrubberduckdev

Hm, the build metadata is there because it's semver2.0 standard, and it helps quickly go back to the actual build and hash that generated a given package.

Is this still an issue?

kzu avatar May 27 '19 18:05 kzu