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
PackageIdentifier: CircuitDiagram.CircuitDiagram version 3.0 #22801
PackageIdentifier: CircuitDiagram.CircuitDiagram version 3.0 #22801
Conversation
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
Hello @vedantmgoyal2009, Please verify the manifest file is compliant with the package manager 1.0 manifest specification. You could also try our Windows Package Manager Manifest Creator Preview. For details on the specific error, see the details link below in the build pipeline. |
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.
You also need to change the file name to match the new PackageIdentifier.
Manifest: The filename must match the PackageIdentifier and ManifestType properties from the manifest. actual 'circuitdiagram.circuitdiagram.yaml', expected 'CircuitDiagram.CircuitDiagram.yaml'
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
Hello @wingetbot! Because this pull request has the p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (
|
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.
Hello @vedantmgoyal2009, |
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