Support v2 of NuGet
Problem to solve
Currently, if you use the GitLab Package Registry to publish NuGet packages, you have to use v3 of NuGet. However, if you are using Chocolatey, this is a problem as Chocolatey only supports v2 of NuGet.
As identified here, it's possible that some customers are using a mix of v2 and v3 and if they are migrating from Artifactory to GitLab, they likely need support for the older version.
Proposal
Support v2 of NuGet to ensure:
- that operating system packages can easily be tested before being published and shared using Chocolatey.org.
- so that custom and internal chocolatey packaging endpoints can be hosted on a GitLab instance
- Affecting above two bullets: As of 2023-05-19 Chocolatey 2.0.0 supports NuGet 3.x Client, however for a chocolatey-using customer organization, the common stable production version of Chocolatey client will likely be v2 for an extended period from this date (24 or more months?) depending on the implications of upgrading to v2 for all existing packages and dependencies, including in-house packages for large organizations.
- That PowerShell module developers can publish powershell modules to pre-production and other custom powershell module gallery.
- As of 2023-05-19 (release of new Chocolatey client), PowerShell Gallery clients still require NuGet v2
- that powershell modules can be easily full-cycle tested before deployment to powershellgallery.com
- So that .NET/C# developers can publish custom chocolately packages to GitLab hosted chocolatey end points.
Reference
Edited by DarwinJS