-
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
GorillaDevs.Ferium version 4.5.2 #140834
GorillaDevs.Ferium version 4.5.2 #140834
Conversation
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
@microsoft-github-policy-service agree |
I'm getting issues with windows defender locally too. After whitelisting the file I'm able to install it and it works fine. |
Hi @theRookieCoder, The package didn't pass a Defender or similar security scan. This might be a false positive and we can rescan tomorrow. (Automated response - build 821.) |
Automatic Validation ended with:
(Automated response - build 821.) |
@wingetbot run |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
I would like to get some help from moderation here. Firstly, this isn't a new manifest, this is an update of an existing one (have I configured something wrong?) I also have no idea how I can resolve the validation error because it is a false positive by Windows Defender. I have already reported the false positive to Microsoft directly and have had no response. |
Automatic Validation ended with:
(Automated response - build 858.) |
Hi @theRookieCoder. Thanks for opening a PR.
Each PR containing a manifest is automatically processed by our GitHub Actions into an Azure DevOps pipeline run, where the package described in the manifest is installed and scanned. The goal of this is to greatly limit the installation of compromised or otherwise potentially unwanted software (PUA).
It's subtle, but the error changed from
Yes, we can apply a waiver for now. Eventually, can the exit code be changed to a 0? |
@wingetbot waivers Add Validation-Executable-Error |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
Thanks for the feedback!
This is a CLI application, so it expects some sort of subcommand or argument to be provided. Is there a way to tell the CI to check the version (run |
From the schema, there are 2 options here:
|
b2859f4
into
microsoft:master
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