microsoft / microsoft/winget-cli
Improve `winget upgrade --all` with installer mismatch
Open
Nobody has claimed this yet.
Area-Output
Command-Upgrade
Issue-Feature
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
Description of the new feature / enhancement
When I run winget upgrade --all and one of the packages can't be upgraded due to the installer type being different from what is currently on the system I don't get informed.
The scenario is described in the Ed Tittel's blog.
Proposed technical implementation details
The upgrade flow should inform me about the installer type change as displayed by winget upgrade <package> when this situation occurs.
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 by tracing the upgrade flow used by winget upgrade --all, then compare its behavior with winget upgrade <package> when installer types differ. Done means the all-packages flow informs the user about the installer type mismatch in the same situation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100