-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New version: Microsoft.WindowsTerminal version 1.18.2681.0 #120906
New version: Microsoft.WindowsTerminal version 1.18.2681.0 #120906
Conversation
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
manifests/m/Microsoft/WindowsTerminal/1.18.2681.0/Microsoft.WindowsTerminal.installer.yaml
Show resolved
Hide resolved
This is probably failing due to |
Hey there! This looks like a duplicate of #120903 |
I think yours is better though...! |
Actually, I think the pipelines are still on WinGet 1.4 |
That it is - but intentionally so; Since 1.6 was released, we are waiting for the 1.6 client to hit the pipelines and for dependencies validation to be enabled. Since Terminal is such a popular package, I would hope that someone like @stephengillie would be able to manually validate the package, although I know that can't be done for every single package that has dependencies. Rather than try to take that PR and figure out if it is correct or needs modification or what the deal is, when working with new features it is easier to make a new PR that references and closes the old one. This way I know that the content should pass a manual validation but it still keeps the history of the previous PR |
@Trenly if you can share your screenshot of this working with the dependencies, I'll merge it. |
Publish pipeline succeeded for this Pull Request. Once you refresh your index, this change should be present. |
winget validate --manifest <path>
?winget install --manifest <path>
?Microsoft Reviewers: Open in CodeFlow