microsoft / microsoft/winget-cli
Allow WINGET to automatically change installer technologies instead of installing with error
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
Relevant area(s)
WinGet CLI
Description of the new feature / enhancement
package(s) have upgrades blocked because newer versions use a different install technology than the current installation. Uninstall each package, then install the newer or specified version.
Proposed technical implementation details
When WINGET detects install technology to be different, allow updating by first uninstalling older version of a product and caching the installed software package name, and then proceed to install it using the version specified via command line or the latest version available.
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 WinGet CLI flow that detects a changed installer technology during an upgrade, including the command-line version-selection path. Trace how uninstall and install are currently handled, then verify that the older product is removed, its package name is retained, and the requested or latest version installs successfully without the technology-mismatch error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100