microsoft / microsoft/winget-cli
Requires updating source every time
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
Sort of a continuation of #2696 because ever since working that one time in my last comment it has not fetched an upgrade for a single package.
This was not the case about a year ago, so I'm either missing something, or this is a newly introduced bug or a design flaw.
The upgrade command is essentially useless because it will say No installed package found matching input criteria. until source update / source reset --force is run.
What is the point of checking for upgrades without updating the local source copy?
Shouldn't winget check the actual source so long as there is internet connection?
Steps to reproduce
Run winget upgrade / winget upgrade --all.
Expected behavior
Packages get upgraded to the latest available versions according to their latest manifests.
Actual behavior
Packages seem to get checked against the local copy of the manifests only which is useless and will continue to show there are no upgrades.
Environment
> winget --info
Windows Package Manager v1.4.10173
Copyright (c) Microsoft Corporation. All rights reserved.
Windows: Windows.Desktop v10.0.19044.2486
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.19.10173.0
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 reproducing winget upgrade and winget upgrade --all with the reported WinGet environment, then compare their behavior with source update and source reset --force. Trace the upgrade command's source-refresh and manifest lookup path; done means upgrades use current manifests without requiring a manual source update.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100