microsoft / microsoft/winget-pkgs
`New-Package` Label applied when versions already exist
Open
Nobody has claimed this yet.
Area-Bots
Area-Validation-Pipeline
Issue-Bug
- Dominant language
- No language data
- Stars
- 11.1k
- Forks
- 9.7k
- Avg merge
- 1h 32m
- Merged PRs (30d)
- 376
Description
In the above PR, several versions of the package already exist in the repo, yet the pipelines applied the New-Package label instead of the New-Manifest Label
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 comparing PR 138984 with PRs 139055, 139051, 139050, and 139220, including the pipeline runs and applied labels. Trace where the pipeline decides between New-Package and New-Manifest; done means packages with existing versions receive New-Manifest rather than New-Package.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100