Update version ranges in nuspec file to use maximum inclusive rather than maximum exclusive #999
Description
Checklist
- I have verified this is the correct repository for opening this issue.
- I have verified no other issues exist related to my problem.
- I have verified this is not an issue for a specific package.
- I have verified this issue is not security related.
What You Are Seeing?
When attempting to upgrade to the latest stable package versions for the 2.x/6.x release of the Chocolatey products, there are issues with resolving package dependencies. This is due in part to a bug in the NuGet.Core assemblies with regard to how maximum exclusive/inclusive versions are handled.
Currently, for Chocolatey GUI, we use the following:
<dependency id="Chocolatey" version="[1.0.0, 2.0.0)" />
This can cause problems for example when you attempt to upgrade to a pre-release 2.0.0 package version, compared to a stable 2.0.0 package version.
To avoid any ambiguity, and prevent confusion going forward, the suggestion is to switch to:
<dependency id="Chocolatey" version="[1.0.0, 1.999.999]" />
That way, the cross over to the 2.0.0 release is clear, and should no longer impact on dependency resolution that is performed.
A similar change has already been made to the version ranges in the upcoming 2.x and 6.x releases.
What is Expected?
There should be no dependency resolution problems when attempting to perform choco upgrade chocolatey when a major version range is being crossed.
How Did You Get This To Happen?
An attempt was made to upgrade to the latest stable package version for all of the Chocolatey products, i.e. 2.x.
System Details
- Operating System: Windows 10
- Windows PowerShell version: 5.1.19041.2364
- Chocolatey CLI Version: 1.3.1
- Chocolatey Licensed Extension version: 5.0.2
- Chocolatey License type: Business
- Terminal/Emulator: PowerShell
Installed Packages
N/AOutput Log
N/AAdditional Context
N/A
Activity