-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
winget upgrade --include-pinned
does not include pinned packages
#2975
Comments
After looking at this more, I realize it may be because the pin types are "Blocking" pins. I would think they should still be listed, though, as it seems to be bad UX to never inform the user of an upgrade, even if they've chosen to require the pin to be removed before upgrade. Especially given that there is a string especially for this purpose -
|
Huh, looks like I completely forgot to use that string. You can get the actual latest available versions with Maybe that is not an intuitive behavior. |
Maybe when |
Also, when the
|
Brief description of your issue
Winget upgrade reports that packages have pins preventing upgrade. Running the command again with
--include-pinned
does not show any additional results, despite me knowing for a fact that at least one pinned package has an upgrade available.Steps to reproduce
Ensure a package reports that it is available for upgrade, such as Microsoft.Office
Pin the package
Run
winget upgrade
- Note that the message indicating pinned packages are present for upgrade is shownRun
winget upgrade --include-pinned
- Note that the pinned package is still not shownExpected behavior
Packages with pins to be shown for upgrade when
--include-pinned
is usedActual behavior
Upgrade - WinGet-2023-02-15-20-54-39.452.log
Upgrade include Pinned - WinGet-2023-02-15-20-54-59.275.log
List Windows SDK - WinGet-2023-02-15-20-55-32.447.log
List Office - WinGet-2023-02-15-20-55-55.297.log
Environment
The text was updated successfully, but these errors were encountered: