Package is listed by winget list with an available upgrade but is silently omitted from winget upgrade
Mantenedores costumam responder em até 2 dias
Ninguém assumiu esta issue ainda.
Avaliação
- Dificuldade
- 4/5
- Tempo estimado
- 3-5 dias
- Facilidade para iniciantes
- 54/100
Direção de pesquisa
Start by comparing the package enumeration paths used by winget list and winget upgrade, using the reported Mozilla Firefox case to trace where the candidate is dropped. Reproduce with the listed commands on Windows and inspect the relevant logs or tests for upgrade enumeration. Done means an available upgrade shown by winget list is included by winget upgrade, or the command explains why it is excluded.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
Relevant area(s)
WinGet CLI
Relevant command(s)
winget list, winget upgrade
Brief description of your issue
Mozilla.Firefox correlates correctly to its installed ARP entry and winget list reports both the installed version and a newer available version from the winget source. The same package never appears in winget upgrade output, under any combination of flags, context or source scoping. No error, no warning, and no non-zero exit code — the package is simply absent from the enumeration.
winget upgrade --id Mozilla.Firefox --exact works and installs the newer version successfully, so the package itself is fine. Only the enumeration path omits it.
This matters for unattended patching: tools that drive winget by enumerating winget upgrade and acting on the result (Winget-AutoUpdate in our case) never see the package as a candidate, so the application is silently never updated. There is nothing in any log to indicate why.
Steps to reproduce
- Install Firefox using the standard Mozilla full (NSIS) installer to the default machine-wide location.
- Wait for a newer Firefox release to become available in the winget source.
- Run
winget list --id Mozilla.Firefox --exact— the package appears with a populated Available column. - Run
winget upgrade— the package is absent.
Expected behavior
A package that winget list reports as having an available newer version should appear in winget upgrade, or winget should explain why it does not.
Actual behavior
> winget list --id Mozilla.Firefox --exact
Name Id Version Available Source
--------------------------------------------------------------------
Mozilla Firefox (x64 en-US) Mozilla.Firefox 157.0.1 159.0 winget
> winget upgrade --include-unknown
Name Id Version Available
-------------------------------------------------------------------------------------------
Cato Client CatoNetworks.CatoClient 6.12.6.9050 6.18.0.9152
Ghost Trap 1.6.10.04 PaperCutSoftware.GhostTrap Unknown 1.6.10.07
Google Chrome Google.Chrome 157.0.8103.38 157.0.8103.39
Microsoft.WindowsAppRuntime.1.4 Microsoft.WindowsAppRuntime.1.4 1.4.5 1.4.7
Microsoft.WindowsAppRuntime.1.7 Microsoft.WindowsAppRuntime.1.7 1.7.3 1.7.9
NetDocuments ndOffice NetDocuments.ndOffice 4.2.1.21157 4.3.1.21397
Zoom Outlook Plugin Zoom.ZoomOutlookPlugin 6.6.0 7.2.0
Zoom Workplace (64-bit) Zoom.Zoom 7.1.48550 7.2.51704
8 upgrades available.
Explicit upgrade works:
> winget upgrade --id Mozilla.Firefox --exact --source winget --silent --accept-package-agreements --accept-source-agreements
Found Mozilla Firefox (en-US) [Mozilla.Firefox] Version 159.0
...
Successfully installed
Environment
Windows Package Manager v1.29.380
Windows: Windows.Desktop v10.0.26200.9711
System Architecture: X64
- Linguagem predominante
- C++
- Estrelas
- 26.6k
- Forks
- 1.8k
- Merge médio
- 3d 10h
- PRs com merge (30d)
- 41
Preparar o ambiente
- Sem Dockerfile nem arquivo Docker Compose
- Tem um modelo de pull request
- Ler o guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de microsoft/winget-cli
-
Issue-Docs Needs-Triage
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 70/100
microsoft/winget-cli#6692 ·
Mantenedores costumam responder em até 2 dias
-
Issue-Docs Possible-Duplicate
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 76/100
microsoft/winget-cli#6493 · 1 comentário ·
Mantenedores costumam responder em até 2 dias
-
WinGetSourceCreator: PackWithMappingFile should verify makeappx.exe exists before invoking itAbertaIssue-Feature
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 68/100
microsoft/winget-cli#6427 ·
Mantenedores costumam responder em até 2 dias
-
Issue-Docs msstore
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 64/100
microsoft/winget-cli#6331 · 1 comentário ·
Mantenedores costumam responder em até 2 dias
-
Command-Source Issue-Bug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 68/100
microsoft/winget-cli#6148 ·
Mantenedores costumam responder em até 2 dias
Todas as issues de microsoft/winget-cli
Issues semelhantes
-
feat
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 65/100
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 68/100
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 75/100
stratum-mining/sv2-tp#167 ·
Mantenedores costumam responder em até 1 dia
-
better error message bug low priority semantics strings
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
Mantenedores costumam responder em até 1 dia
-
Sign up button opens the Sign in page instead of the Sign up page for Enterprise edition serversAbertaauth bug ui/ux
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
MerginMaps/mobile#4795 ·
Mantenedores costumam responder em até 2 dias