Skip to content

New version: jm2.Tributary version 0.2.1#355588

Open
jm2 wants to merge 1 commit intomicrosoft:masterfrom
jm2:jm2.Tributary-0.2.1-3bd6781f-9b27-427f-8343-a1e2f6d92e3d
Open

New version: jm2.Tributary version 0.2.1#355588
jm2 wants to merge 1 commit intomicrosoft:masterfrom
jm2:jm2.Tributary-0.2.1-3bd6781f-9b27-427f-8343-a1e2f6d92e3d

Conversation

@jm2
Copy link
Copy Markdown
Contributor

@jm2 jm2 commented Apr 5, 2026

Checklist for Pull Requests

Manifests

  • Have you checked that there aren't other open pull requests for the same manifest update/change?
  • This PR only modifies one (1) manifest
  • 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.12 schema?

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


Microsoft Reviewers: Open in CodeFlow

@wingetbot
Copy link
Copy Markdown
Collaborator

Validation Pipeline Run WinGetSvc-Validation-136-355588-20260405-1

@wingetbot wingetbot added New-Manifest Internal-Error An unidentified error occurred in the validation pipeline labels Apr 5, 2026
@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Attention This work item needs to be reviewed by a member of the core team. label Apr 5, 2026
@jm2
Copy link
Copy Markdown
Contributor Author

jm2 commented Apr 7, 2026

Is this actually a failure on my end or just a validation pipeline failure?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Internal-Error An unidentified error occurred in the validation pipeline Needs-Attention This work item needs to be reviewed by a member of the core team. New-Manifest

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants