microsoft / microsoft/winget-cli
WinGet upgrade breaks when additional installer type in new manifest
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
Brief description of your issue
I added portable ZIP to PowerShell manifest:
This made winget upgrade break for folks that had installed earlier versions, with error message:
winget upgrade Microsoft.Powershell
A newer version was found, but the install technology is different from the current version installed. Please uninstall the package and install the newer version.
https://github.com/PowerShell/PowerShell/issues/25068#issuecomment-2677087143
Steps to reproduce
See linked issue
Expected behavior
If the same installer type is available in a newer version of a manifest -> Keep using it.
Actual behavior
Chose portable?
Environment
I havent reproduced, see linked issue.
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 reviewing the linked PowerShell issue and winget-pkgs pull request 231998, then trace the winget upgrade path for manifests with multiple installer types. Done means an installed package continues using the same installer type when a newer manifest adds another type, without producing the reported incompatibility error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, powershell
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100