microsoft / microsoft/winget-pkgs
[New Feature]: Validate against Correlation collisions
- Dominant language
- No language data
- Stars
- 11.1k
- Forks
- 9.7k
- PR merge metrics
- PR metrics pending
Description
### Description of the new feature/enhancement
With the ever-growing number of manifests in the repository, it's inevitable that multiple packages would have the same correlation data.
During Installer Validation, the pipelines should throw a warning if the installed package correlates to one or more package identifiers other than the one the PR is for
### Proposed technical implementation details (optional)
_No response_
Contributor guide
Research direction
Start by tracing the Installer Validation pipelines and how an installed package is correlated to package identifiers. Determine where validation can compare those identifiers with the PR's package, then make the pipeline warn when additional correlations are found. Done means collision cases produce a warning without blocking valid installation.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd, devops, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100