-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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: LeiGod.LeiGodAcc version 7.0.5.8 #29801
New: LeiGod.LeiGodAcc version 7.0.5.8 #29801
Conversation
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please close and reopen the PR to rerun pipelines.
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
Hello @SpecterShell, |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
Hello @SpecterShell, |
Hello @SpecterShell, |
/AzurePipelines run |
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
/AzurePipelines run |
No commit pushedDate could be found for PR 29801 in repo microsoft/winget-pkgs |
So how to fix it? |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
Hello @SpecterShell, The application included in this pull request failed to pass the Installers Scan test. This test is designed to ensure that the application installs on all environments without warnings. For more details on this error, see Binary validation errors. Please check to ensure the installer URL is correct and update the URL and the Hash if a change is made. |
Hello @SpecterShell, |
I don't think an administrator would be able to do anything with this PR because all PRs have to go through Dynamic Analysis, but it's failing since the application is likely falsely flagged as PUA, malware, spyware, etc. either by Microsoft Defender or other anti-virus software. |
I just found https://docs.microsoft.com/en-us/windows/package-manager/package/winget-validation, and you're correct. Thanks. |
winget validate --manifest <path>
?winget install --manifest <path>
?Note:
<path>
is the name of the directory containing the manifest you're submitting.