This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Handle Multiple Major Versions of One Package #793
Milestone
You can continue the conversation there. Go to discussion →
Brief description of your issue
winget is not able to handle the situation where there are multiple versions of the same package installed, based on name. An example of this in action are .NET runtimes, where you often have multiple major versions installed side-by-side.
Steps to reproduce
winget upgrade --all
Expected behavior
Ideally, I expect .NET Core Runtime 3 to be considered separate from .NET Core Runtime 5. When winget checks for upgrades, it should only look for upgrades relating to that major version.
Actual behavior
winget is seeing both .NET Core Runtime 3 (version 3.1.11.29516 on my computer) and .NET Core Runtime 5 (version 5.0.3.29723 on my computer) and reporting that an upgrade to version 5.0.4.29817 is available for both runtimes.
winget upgrade
:winget upgrade --all
:Environment
The text was updated successfully, but these errors were encountered: