-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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 package: Autodesk.NavisworksManage.2022 version 19.0.136606 #205933
New package: Autodesk.NavisworksManage.2022 version 19.0.136606 #205933
Conversation
/AzurePipelines run |
/AzurePipelines run |
/AzurePipelines run |
1 similar comment
/AzurePipelines run |
/AzurePipelines run |
/AzurePipelines run |
manifests/a/Autodesk/NavisworksManage2022/2022/Autodesk.NavisworksManage2022.installer.yaml
Outdated
Show resolved
Hide resolved
manifests/a/Autodesk/NavisworksManage2022/2022/Autodesk.NavisworksManage2022.locale.en-US.yaml
Outdated
Show resolved
Hide resolved
manifests/a/Autodesk/NavisworksManage2022/2022/Autodesk.NavisworksManage2022.yaml
Outdated
Show resolved
Hide resolved
manifests/a/Autodesk/NavisworksManage2022/2022/Autodesk.NavisworksManage2022.installer.yaml
Outdated
Show resolved
Hide resolved
/AzurePipelines run |
Hello @rovabunw, Please verify the manifest file is compliant with the package manager 1.9 manifest specification. Make sure the ID is of the form publisher.appname and that the folder structure is manifests\partition\publisher\appname\version.
Be sure to use a tool like VSCode to make sure the manifest YAML syntax is correct. You can also validate your manifest using the For details on the specific error, see the details link below in the build pipeline. Template: msftbot/validationError/manifest/content |
/AzurePipelines run |
Hello @rovabunw, Please verify the manifest file is compliant with the package manager 1.9 manifest specification. Make sure the ID is of the form publisher.appname and that the folder structure is manifests\partition\publisher\appname\version.
Be sure to use a tool like VSCode to make sure the manifest YAML syntax is correct. You can also validate your manifest using the For details on the specific error, see the details link below in the build pipeline. Template: msftbot/validationError/manifest/content |
Automatic Validation ended with:
(Automated response - build 949.) |
Hello @rovabunw, This pull request has been automatically marked as stale because it has been marked as requiring author feedback but has not had any recent activity. It will be closed if no further activity occurs within 3 days of this comment. Template: msftbot/noRecentActivity |
@stephengillie this PR should be blocked: similar to #207762 (comment) |
Hello @rovabunw, This package appears to require user interaction to install. This PR is blocked until support for interactive installer search filtering is implemented in: Be sure to add your 👍 to the issue to help raise the priority and avoid posting "Me too!" messages to respect those who have subscribed to the issue. Template: msftbot/blockingIssue/interactiveOnlyInstall |
Hello @rovabunw, Thank you for your contribution. This Pull Request has been identified as being blocked by a known issue. Since there has been no recent activity on this PR, it will be automatically closed. Please re-submit your PR with the necessary changes once the blocking issue is resolved. If an issue has not been linked, please tag whomever added the Blocking-Issue label for additional information. Template: msftbot/noRecentActivity/blockingIssue |
Checklist for Pull Requests
Manifests
winget validate --manifest <path>
?winget install --manifest <path>
?Note:
<path>
is the directory's name containing the manifest you're submitting.Microsoft Reviewers: Open in CodeFlow