Package is listed by winget list with an available upgrade but is silently omitted from winget upgrade

Abierto
#6,661 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
54/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
cpp
Área
backend, cli

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Command-List Command-Upgrade Issue-Bug
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
  1. Install Firefox using the standard Mozilla full (NSIS) installer to the default machine-wide location.
  2. Wait for a newer Firefox release to become available in the winget source.
  3. Run winget list --id Mozilla.Firefox --exact — the package appears with a populated Available column.
  4. 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
Lenguaje dominante
C++
Estrellas
26.6k
Forks
1.8k
Merge medio
3 d 10 h
PR fusionados (30 d)
41

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de microsoft/winget-cli

Todos los issues de microsoft/winget-cli

Issues similares

Más issues de C++

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.