microsoft / microsoft/winget-pkgs

[New Feature]: Manifest version 1.6.0 should have been flagged from the pipeline

Open
#380,264 12 comments 3 reactions 0 assignees View on GitHub
Area-Validation-Pipeline Issue-Feature
Dominant language
No language data
Stars
11.1k
Forks
9.7k
Avg merge
1h 32m
Merged PRs (30d)
616

Description

### Description of the new feature/enhancement

Follow up from https://github.com/microsoft/winget-pkgs/pull/373842#issuecomment-4549587738 and how common new commers uses `ManifestVersion: 1.6.0` instead of latest, I think any PR submitted with said `ManifestVersion` should have been flagged as https://github.com/microsoft/winget-pkgs/labels/Manifest-Version-Deprecated to match with the docs deprecation label:

Image

Just like what's already did for even older schema versions (e.g.: https://github.com/microsoft/winget-pkgs/pull/378423#issuecomment-4529529552).

### Proposed technical implementation details (optional)

_No response_

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the manifest validation pipeline and the linked pull request examples, especially the existing handling for older schema versions. Trace where ManifestVersion values are checked and labels are applied. Done means submissions using ManifestVersion 1.6.0 receive the Manifest-Version-Deprecated label consistently with older deprecated versions.

Written by the indexing model from the issue text.

Assessment

Domain
ci-cd
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.