microsoft / microsoft/winget-pkgs

[New Feature]: Validate installer availability in Validation Pipeline during package version removal

Open
#295,640 1 comment 5 reactions 0 assignees View on GitHub
Area-Validation-Pipeline Issue-Feature Moderator-Approved
Dominant language
No language data
Stars
11.1k
Forks
9.7k
PR merge metrics
PR metrics pending

Description

### Description of the new feature/enhancement

When a PR is submitted to remove a package version, the Validation Pipeline can check if the installer(s) are still available. If an installer is still available, a warning can be posted to the pull request.
This warning should not block the PR from merging, as there are many valid reasons for removal even if the installer is still available (e.g., move this package version to another package identifier.).
I'm aware that Stephen's automation already performs a similar check (e.g., https://github.com/microsoft/winget-pkgs/pull/289633#issuecomment-3250874699), but I think if incorporating it into the validation pipeline might provide faster, immediate feedback to the author.

### Proposed technical implementation details (optional)

_No response_

Contributor guide

Open the contributing guide

Research direction

Start by locating the repository's Validation Pipeline and review the existing installer-availability automation referenced in the issue. Define how package-version removal is detected, where a non-blocking pull request warning should appear, and how the behavior can be tested; the work is done when valid removals remain mergeable while available installers produce immediate feedback.

Written by the indexing model from the issue text.

Assessment

Domain
ci-cd
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.