Support Semantic Versioning 2.0.0 (semver) #1610
Comments
|
Since this hasn't been officially answered. I'll unofficially answer it. Deducing from "https://chocolatey.org/api/v2/" I'd say Chocolatey is still using nuget v2. @ferventcoder has some comments somewhere (paraphrasing) saying that nuget v3 is not in a finished state yet. (Don't know if it still holds true as of today.) |
ferventcoder
changed the title
|
@watashiSHUN Chocolatey != NuGet. Chocolatey uses NuGet and enhances, but the two are not quite equal in terms of what they support. We are working on supporting SemVer v2 though, and we hoped to have it ready in 0.10.11. @bcurran3 is correct that Chocolatey has enhancements on top of NuGet v2 - we have it on the roadmap to move to NuGet vNewer, but it's not the easiest upgrade to support as it is not a 1:1, so we want to have all of the different things for testing infra in place prior to the upgrade to catch any unexpected issues. |
|
Added this to the backlog, I thought we actually had an issue in here somewhere but I was unable to locate it. Thanks for writing that up! |
|
@ferventcoder, do you have an idea when this might come? Would a PR help? I'm interested in it for 2 reasons:
Thanks |
|
@Thilas while this would get into Chocolatey itself in vNext, it will also need to be added to Chocolatey.org to work up there. I wonder if we have an issue on it up there yet? |
|
@ferventcoder, what do you mean? That we can already test it on choco itself? Is there anything I can do to help? |
|
Does getting to semver 2.0.0 require upgrading nuget? |
|
Is there any timeline for the this will be included? |
|
We have a hoped timeline, but it needs to make the cut for releasing bits. Then we'll need to make changes to support it on Chocolatey.org as well. |
Previously, when running some of the pack scenarios in Visual Studio, some of the resulting packages contained the entire contents of the debug folder, which slowed the the test as it took longer to pack. This add a dependency and empty files element, so only the nuspec is packed.
…ing zeros Also adds install tests for packages with a forth part zero
…ing zeros Also adds install tests for packages with a forth part zero
…ing zeros Also adds install tests for packages with a forth part zero
… with leading zeros Also adds install tests for packages with a forth part zero
…stall with leading zeros Also adds install tests for packages with a forth part zero
… zeros These tests are to ensure that the version normalization on pack with the new NuGet assemblies is consistent into the future. There were already tests for removing semver v2 build metadata and that four part versions still work. This adds tests to ensure that leading zeros are removed, and that a zero in the fourth part of the version will be trimmed down to three parts. https://learn.microsoft.com/en-us/nuget/concepts/package-versioning#normalized-version-numbers
Previously, when running some of the pack scenarios in Visual Studio, some of the resulting packages contained the entire contents of the debug folder, which slowed the the test as it took longer to pack. This add a dependency and empty files element, so only the nuspec is packed.
…s with leading zeros Also adds install tests for packages with a forth part zero
… zeros These tests are to ensure that the version normalization on pack with the new NuGet assemblies is consistent into the future. There were already tests for removing semver v2 build metadata and that four part versions still work. This adds tests to ensure that leading zeros are removed, and that a zero in the fourth part of the version will be trimmed down to three parts. https://learn.microsoft.com/en-us/nuget/concepts/package-versioning#normalized-version-numbers
Previously, when running some of the pack scenarios in Visual Studio, some of the resulting packages contained the entire contents of the debug folder, which slowed the the test as it took longer to pack. This add a dependency and empty files element, so only the nuspec is packed.
…s with leading zeros Also adds install tests for packages with a forth part zero
|
Due to the uplift to the latest NuGet Client assemblies, this is now supported within Chocolatey CLI. |
gep13
removed
the
Requires NuGet.Client Change
|
🎉 This issue has been resolved in version 2.0.0 🎉 The release is available on: Your GitReleaseManager bot 📦🚀 |
what version of nuget is chocolatey using? looking at
NuGet.exeunder.nuget/, I am getting 1.7.0 which is pretty ancient. Anyway, right now I can not pack with version number following SemVer2.0.0:but this is supported in nuget4.3.0+:
The text was updated successfully, but these errors were encountered: