microsoft / microsoft/winget-cli

Add a check for a PR for a listing of a tool installed by winget that is waiting to be merged in feeds packages repo

Open
#3,443 2 comments 4 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

Description of the new feature / enhancement

As a user/admin/developer using winget for tool installs/upgrades

  • I should be able to run Winget install or winget upgrade and install any package that is currently waiting to be published in the feed
  • Clear notification that a new version of this tool is available but is not yet available via listed winget feeds due to a PR for this waiting to be merged
  • Notification in this case is clear to try again later
  • option to override and attempt an upgrade anyway

This would negate lots of repeated issues getting raised to partner teams (like PowerShell, vs code and 3rd party partners) where there is a wait for the PR for an updated Package to be merged and made available whether in the winget-pkgs repo or other private package feeds
Optionally should allow for a defer until available checker and this can then auto check on a regular cadence
Perhaps the above is better to be documented than implemented in the tool itself

(Could have already been raised but could not see this ask when searching the issues so apologies if this has been asked)

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

The issue names no files, tests, or entry points. First clarify whether the desired outcome is documentation or a change to winget install and upgrade behavior, then trace how feed availability is handled. Done would require an agreed scope, clear notification and retry or override behavior, and tests or documentation covering it.

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
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.