-
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
Fixing jq manifest according to 1.4.0 schema #116426
Fixing jq manifest according to 1.4.0 schema #116426
Conversation
To be honest, when I tested this manifest I did get
However, when I typed |
The symlink likely wasn’t added due to not being run in admin mode. See |
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.
This PR doesn’t actually change anything, as the items being at the root level of the manifest functions the same as them being at the installer level
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
RockyMM, The check-in policies require a moderator to approve PRs from the community. Our moderators are community volunteers, please be patient and allow them sufficient time to review your submission. Template: msftbot/requiresApproval/moderator |
2270ce9
into
microsoft:master
Hello RockyMM, Template: msftbot/validationCompleted |
Publish pipeline succeeded for this Pull Request. Once you refresh your index, this change should be present. |
Thanks for the tip. I will try it out. As for the content of my PR, at least now the content is according to schema. I know it's not much but it's honest work 😁 |
winget validate --manifest <path>
?winget install --manifest <path>
?Note:
<path>
is the name of the directory containing the manifest you're submitting.Microsoft Reviewers: codeflow:open?pullrequest=#116426