microsoft / microsoft/winget-cli
PowerShell - Make `Update-WinGetPackage` work just like `winget upgrade` (with no arguments)
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
Description of the new feature / enhancement
winget upgrade shows a list of installed programs with a newer version available, if any. It also has --include-pinned and --include-unknown.
I find no similar functionality in Microsoft.WinGet.Client. I'd expect Update-WinGetPackage to work the same, so I add this as a feature request.
- Or add a parameter (switch)
-ListAvailableUpdates?
Proposed technical implementation details
Make Update-WinGetPackage act like winget upgrade.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Update-WinGetPackage command in Microsoft.WinGet.Client and compare its current behavior with winget upgrade without arguments. Review how --include-pinned and --include-unknown are exposed, then verify that the command lists installed packages with available updates and handles those options consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, powershell
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100