microsoft / microsoft/winget-pkgs

[Bug]: Winget is reporting a .NET 6.0 SDK package as an update for a .NET 5.0 SDK installation.

Open
#38,045 4 comments 16 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area-Matching Issue-Bug
Dominant language
No language data
Stars
11.1k
Forks
9.7k
Avg merge
1h 32m
Merged PRs (30d)
376

Description

Brief description of your issue

On executing the "winget upgrade" command, it's reporting that an update is available for Microsoft .NET SDK.
Now the problem is that while the given version number refers to the latest .NET 5 SDK which is installed on my system, the available package version belongs to the latest .NET 6 SDK.
image

Steps to reproduce

Have the latest version .NET 5.0 SDK installed.
And run command "winget upgrade" from the terminal.

Expected behavior

On executing command "winget upgrade", an update package for .NET 5 SDK should be reported, if available.

Actual behavior

On executing command "winget upgrade", an update for Microsoft .NET SDK is being reported with the current version number being of .NET 5 SDK but with the available package version number being of .NET 6 SDK.
Updating Microsoft .NET SDK using the command "winget install Microsoft.dotnet -i -s winget", results in .NET 6 SDK is being installed.
Subsequent execution of the "winget upgrade" command results in the same available update being reported again because obviously .NET 5 SDK is not being updated because obviously its not an update for .NET 5 SDK.
image

Environment
Windows Package Manager v1.1.13405
Copyright (c) Microsoft Corporation. All rights reserved.                                                               
Windows: Windows.Desktop v10.0.22000.376
Package: Microsoft.DesktopAppInstaller v1.16.13405.0

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the report with the latest .NET 5.0 SDK installed and run "winget upgrade" in the environment described. Trace how the Microsoft .NET SDK package is selected and compare the installed and available versions; done means .NET 5 users are offered only a compatible .NET 5 update, and the repeated false upgrade no longer appears.

Written by the indexing model from the issue text.

Assessment

Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.