microsoft / microsoft/winget-pkgs
Regression: Azure Pipelines failing on manifest that contains dependencies
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 11.1k
- Forks
- 9.7k
- Avg merge
- 1h 32m
- Merged PRs (30d)
- 376
Description
I'm facing an unknown issue preventing my package from being validated. Refer to https://github.com/microsoft/winget-pkgs/pull/132245, https://github.com/microsoft/winget-pkgs/pull/133023, and https://github.com/microsoft/winget-pkgs/pull/135613.
I recently ran a test to prove a change in my package wasn't a change in my code. 6.1.0 was originally submitted in https://github.com/microsoft/winget-pkgs/pull/132002 and validated successfully. The exact same manifest (and therefore, installer) with a different version number failed validation today (https://github.com/microsoft/winget-pkgs/pull/135622).
I am unable to diagnose this issue further do to the validation logs seemingly being unavailable to the public.
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 the validation results for the manifests in pull requests 132002, 135622, 132245, 133023, and 135613. Investigate the Azure Pipelines validation logs, if available, and determine why an otherwise identical manifest containing dependencies fails. Done means the regression is explained and a reproducible validation fix or actionable diagnosis is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100