microsoft / microsoft/winget-cli
Provide a way to upgrade packages which do not change versions
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
There are some packages which do not change their marketing version or display version in between builds. Some examples of this are Aiursoft.Kahla, Chrome Beta, and many of the KDE nightlies.
Because the version doesn’t change at all, there is currently no way to determine if a user is on the latest version or not and so the user will not be upgraded.
Proposed technical implementation details
When an application is installed through winget, store the hash in the installed.db or elsewhere
When running winget upgrade, check to ensure the stored hash matches the manifest. If the hash does not match, an upgrade is required.
If the hash does not exist, the application was installed outside of winget. Appropriate behavior should be considered as to whether or not these packages are selected for 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 by reviewing the proposed installed.db storage and the winget upgrade flow. Define how stored hashes should be compared with manifest hashes, and decide the behavior for packages without a stored hash. Done means unchanged-version packages can be identified for upgrade without ambiguous handling of packages installed outside winget.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100