Skip to content
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

[Zip] New Package: Helm.Helm 3.10.1 #86104

Merged
merged 3 commits into from
Feb 9, 2023
Merged

[Zip] New Package: Helm.Helm 3.10.1 #86104

merged 3 commits into from
Feb 9, 2023

Conversation

ssrahul96
Copy link
Contributor

@ssrahul96 ssrahul96 commented Oct 23, 2022

  • Have you signed the Contributor License Agreement?
  • Have you checked that there aren't other open pull requests for the same manifest update/change?
  • Have you validated your manifest locally with winget validate --manifest <path>?
  • Have you tested your manifest locally with winget install --manifest <path>?
  • Does your manifest conform to the 1.2 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.


Microsoft Reviewers: Open in CodeFlow

fix for #30128

@wingetbot
Copy link
Collaborator

Service Badge  Service Badge  

@wingetbot
Copy link
Collaborator

/AzurePipelines run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@ssrahul96
Copy link
Contributor Author

package with zip file microsoft/winget-cli#2500

@wingetbot wingetbot added the Manifest-Validation-Error Manifest validation failed label Oct 23, 2022
@ghost
Copy link

ghost commented Oct 23, 2022

Hello @ssrahul96,

The package manager bot determined that the metadata was not compliant.

Please verify the manifest file is compliant with the package manager 1.2 manifest specification.
Make sure the ID is of the form publisher.appname and that the folder structure is manifests\partition\publisher\appname\version.
Note: The path and "PackageIdentifier" are case sensitive.
Be sure to use a tool like VSCode to make sure the manifest YAML syntax is correct.

You could also try our Windows Package Manager Manifest Creator or the YamlCreate script.

For details on the specific error, see the details link below in the build pipeline.

Template: msftbot/validationError/manifest/metadata

@ghost ghost added the Needs-Author-Feedback This needs a response from the author. label Oct 23, 2022
@ssrahul96 ssrahul96 changed the title added helm [Zip] New Package: Helm.Helm 3.10.1 Oct 23, 2022
ItzLevvie
ItzLevvie previously approved these changes Oct 23, 2022
@ghost ghost added the Moderator-Approved One of the Moderators has reviewed and approved this PR label Oct 23, 2022
@ssrahul96 ssrahul96 marked this pull request as draft October 24, 2022 04:13
@ghost ghost assigned ssrahul96 Oct 24, 2022
@ghost
Copy link

ghost commented Oct 24, 2022

Hello @ssrahul96,

The package manager bot determined changes have been requested to your PR.

Template: msftbot/changesRequested

Co-authored-by: Karan09 <[email protected]>
@ghost ghost added Needs-Attention This work item needs to be reviewed by a member of the core team. and removed Needs-Author-Feedback This needs a response from the author. Manifest-Validation-Error Manifest validation failed Moderator-Approved One of the Moderators has reviewed and approved this PR labels Oct 24, 2022
@wingetbot
Copy link
Collaborator

/AzurePipelines run

@ghost ghost removed the Needs-Attention This work item needs to be reviewed by a member of the core team. label Oct 24, 2022
@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@wingetbot wingetbot added the Manifest-Validation-Error Manifest validation failed label Oct 24, 2022
@ghost
Copy link

ghost commented Oct 24, 2022

Hello @ssrahul96,

The package manager bot determined that the metadata was not compliant.

Please verify the manifest file is compliant with the package manager 1.2 manifest specification.
Make sure the ID is of the form publisher.appname and that the folder structure is manifests\partition\publisher\appname\version.
Note: The path and "PackageIdentifier" are case sensitive.
Be sure to use a tool like VSCode to make sure the manifest YAML syntax is correct.

You could also try our Windows Package Manager Manifest Creator or the YamlCreate script.

For details on the specific error, see the details link below in the build pipeline.

Template: msftbot/validationError/manifest/metadata

@ghost ghost added the Needs-Author-Feedback This needs a response from the author. label Oct 24, 2022
@ghost ghost added the Needs-Author-Feedback This needs a response from the author. label Oct 24, 2022
@ghost ghost added the Moderator-Approved One of the Moderators has reviewed and approved this PR label Oct 27, 2022
@ghost ghost added the No-Recent-Activity No activity has occurred on this work item for seven days. label Nov 4, 2022
@ghost
Copy link

ghost commented Nov 4, 2022

Hello @ssrahul96,

This pull request has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within 7 days of this comment.

Template: msftbot/noRecentActivity

@ItzLevvie
Copy link
Contributor

@msftbot .zip

@ghost ghost added .zip Blocking-Issue Manifest validation is blocked by a known issue. and removed No-Recent-Activity No activity has occurred on this work item for seven days. labels Nov 9, 2022
@ssrahul96 ssrahul96 marked this pull request as ready for review January 7, 2023 04:01
@Trenly
Copy link
Contributor

Trenly commented Feb 9, 2023

@wingetbot run

@wingetbot
Copy link
Collaborator

/AzurePipelines run

@microsoft-github-policy-service microsoft-github-policy-service bot removed Manifest-Validation-Error Manifest validation failed Blocking-Issue Manifest validation is blocked by a known issue. labels Feb 9, 2023
@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@microsoft-github-policy-service microsoft-github-policy-service bot removed the Needs-Author-Feedback This needs a response from the author. label Feb 9, 2023
@Trenly
Copy link
Contributor

Trenly commented Feb 9, 2023

[Policy] Reset Feedback

@microsoft-github-policy-service microsoft-github-policy-service bot removed the Moderator-Approved One of the Moderators has reviewed and approved this PR label Feb 9, 2023
@wingetbot wingetbot added Azure-Pipeline-Passed Validation pipeline passed. There may still be manual validation requirements. Validation-Completed Validation passed labels Feb 9, 2023
@microsoft-github-policy-service
Copy link
Contributor

wingetbot,

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

@microsoft-github-policy-service microsoft-github-policy-service bot added the Moderator-Approved One of the Moderators has reviewed and approved this PR label Feb 9, 2023
@microsoft-github-policy-service
Copy link
Contributor

Hello microsoft-github-policy-service[bot],
Validation has completed.

Template: msftbot/validationCompleted

@microsoft-github-policy-service microsoft-github-policy-service bot merged commit 5ccb183 into microsoft:master Feb 9, 2023
@wingetbot
Copy link
Collaborator

Publish pipeline succeeded for this Pull Request. Once you refresh your index, this change should be present.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Azure-Pipeline-Passed Validation pipeline passed. There may still be manual validation requirements. Moderator-Approved One of the Moderators has reviewed and approved this PR Publish-Pipeline-Succeeded Validation-Completed Validation passed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants