microsoft / microsoft/winget-cli

Suggest WinGet upgrade when newer manifest schema versions are detected in community repository

Open
#6,209 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Issue-Feature
Dominant language
C++
Stars
26.4k
Forks
1.8k
Avg merge
1d 11h
Merged PRs (30d)
15

Description

Relevant area(s)

WinGet CLI

Description of the new feature / enhancement

When the community repository (winget-pkgs) contains manifests with a newer schema version than the installed version of WinGet fully supports, this is a strong signal that a newer version of WinGet is available. While WinGet does not ignore these manifests, it may not offer the full behavior and features defined by the newer schema version. The user has no way of knowing they are missing out on supported functionality.

WinGet should detect when it encounters manifest schema versions newer than what it fully supports and inform the user that an upgrade to WinGet is likely available. This could be a one-time notification per session, a message during winget upgrade, or a similar low-friction mechanism.

Why this matters:

  • Users running older versions of WinGet may not realize they are missing supported functionality from newer manifest schema versions.
  • The community repository evolves faster than many users update their tooling — a gentle nudge bridges that gap.
  • This improves the overall user experience by making version currency visible without requiring users to manually check.

Considerations:

  • The notification should be informative, not blocking — it should not prevent WinGet from completing its current operation.
  • Frequency and suppression controls should be considered (e.g., only notify once per day or per session).
  • Group Policy should be able to suppress or control this behavior in managed environments.
Proposed technical implementation details

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the WinGet CLI flow that encounters community-repository manifests and the winget upgrade operation. Trace how manifest schema versions are detected, then define where a non-blocking upgrade notice would fit, including session frequency and Group Policy considerations. Done means the behavior is specified and covered for newer schemas without interrupting the current operation.

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
Quiet
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.