-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
[Zip][Portable] BurntSushi.ripgrep.MSVC 13.0.0 #88066
Conversation
@msftbot zip |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
Hello @Trenly, The package manager bot determined that the metadata was not compliant. Please verify the manifest file is compliant with the package manager 1.2 manifest specification. You could also try our Windows Package Manager Manifest Creator or the YamlCreate script. For details on the specific error, see the details link below in the build pipeline. Template: msftbot/validationError/manifest/metadata |
/AzurePipelines run |
There was an error handling pipeline event 375ce6f6-d3ed-4ef7-957d-56aa0d24344f. |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
Hello @Trenly, The pull request encountered an internal error and has been assigned to a developer to investigate. Template: msftbot/validationError/internalError |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
@wingetbot waivers Add Validation-Executable-Error |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
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>
?Note:
<path>
is the name of the directory containing the manifest you're submitting.Microsoft Reviewers: Open in CodeFlow