Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SemVer 2.0 issue with InjectModuleinitializer and TFS Package Management Feed #16

Open
realrubberduckdev opened this issue Oct 22, 2018 · 1 comment

Comments

@realrubberduckdev
Copy link

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.

@kzu
Copy link
Owner

kzu commented May 27, 2019

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants