microsoft / microsoft/winget-pkgs
[New Feature]: Detect if a package is removed, if the CDN is down, or if the developer changed hosts.
Open
Nobody has claimed this yet.
Issue-Feature
- Dominant language
- No language data
- Stars
- 11.1k
- Forks
- 9.7k
- Avg merge
- 1h 32m
- Merged PRs (30d)
- 376
Description
Description of the new feature/enhancement
Have seen this pattern in a couple of places recently:
- Apparently the developer's host has a network issue,
- PRs are opened to remove the developer's packages.
- Packages become available again.
- PRs sometimes caught and closed, and sometimes merged.
Seen in:
- https://github.com/microsoft/winget-pkgs/pull/162231 (Package unavailable then available again)
- https://github.com/microsoft/winget-pkgs/issues/162187#issuecomment-2222960308
Proposed technical implementation details (optional)
Not exactly sure, but maybe bulk removals should be grouped in some way, and these verified against the developer's status page (if they have one).
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 reviewing PR 162231 and issue 162187, the two examples cited in the description. Define how temporary package removal, CDN outages, and host changes would be detected and grouped, and what verification would prevent erroneous removals; the issue does not name implementation files or tests.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100