PR #436031 - new package stuck in Validation-Domain due error on my part; how to proceed?

[Derell Licht (DerellLicht)]

I had submitted this PR two weeks ago, it has gone through "all checks have passed" and was in Needs-Attention, but then I accidentally closed the PR; I immediately re-opened it, but it had already dropped Needs-Attention, and unassigned the reviewer.

I have sent further posts asking for the PR to be re-activated, but there has been no further action for the past two weeks. Is there any way to get the bots to review this PR and get it active again?

[Serge Yudin (yudin-s)]

Reopening did not make the PR irrecoverable. The current PR still has the active labels that matter here: Azure-Pipeline-Passed, Validation-Domain, New-Package, and Validation-Guide.

The part that cannot be self-triggered is the validation/admin step. Your later @wingetbot run comment already got the important signal: Commenter does not have sufficient privileges. The validation guide says a moderator can re-run validation, but Validation-Domain specifically needs Windows Package Manager administrator review; community moderators cannot waive that label.

So I would not open a duplicate PR just to wake the bot. The useful next comment on the PR is evidence for the domain review, for example:

• the official publisher/package page (PackageUrl) that leads to the installer;
• the exact version-specific download page/release page;
• why the GitLab installer URL is publisher-controlled for this package;
• confirmation that the manifest uses the direct/final URL rather than a redirect/shortener.

After that, it is mostly queue/admin review, not another pipeline run you can force yourself. If it sits much longer, the guide points to the WinGet-pkgs Matrix room as the quicker place to ask whether the Validation-Domain review is still queued.

If this matches what happened to your PR, please mark the answer so the next contributor does not chase the @wingetbot run path from a non-moderator account.

[Derell Licht (DerellLicht)]

Okay, I posted your recommended data into my PR; hopefully that will get the PR active again...
#436031 (comment)