microsoft / microsoft/winget-cli
Upgrading to the best architecture for a package
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
When I have an emulated version of a package and an upgrade becomes available for my native architecture I would like to be informed, and I would like the default experience for upgrade be to take the native version.
There should also be settings so I can override this default behavior to keep emulated versions during upgrade. Sometimes I'm testing the emulated version of the software on a different architecture of hardware.
Proposed technical implementation details
No response
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
The issue names no files, tests, or entry points. Begin by locating WinGet's upgrade flow and its architecture-selection behavior, then define how native-package notifications, the default upgrade choice, and an override setting should work. Done requires agreed behavior and coverage for native and emulated upgrade scenarios.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100