Repository navigation
New version: LoopTroopAI.LoopTroop version 0.5.9 - #438396
Merged
microsoft-github-policy-service[bot] merged 1 commit intoSep 21, 2026
Merged
microsoft-github-policy-service[bot] merged 1 commit into
microsoft-github-policy-service[bot] merged 1 commit into
Conversation
Contributor
|
|
wingetvalidator-prod
Bot
added
the
New-Manifest
wingetvalidator-prod
Bot
added
Azure-Pipeline-Passed
Contributor
|
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 |
LoopTroop (looptroop-ai)
added a commit
to looptroop-ai/LoopTroop
that referenced
this pull request
Sep 21, 2026
Both Windows package feeds have accepted their first submission — Chocolatey approved `looptroop` on 3 September, `microsoft/winget-pkgs` merged `LoopTroopAI.LoopTroop` on 19 September — so the two channels stop being documented as unavailable and start publishing like any other. * Every stable release publishes to both. `PUBLISH_CHOCOLATEY` and `PUBLISH_WINGET` were never set, which is why seven releases published nothing to either feed without failing; the remaining variable gates the AUR alone, where the obstacle is not a queue but the absence of an account. Neither channel gates a release: each submission joins a queue somebody else works and is reported as submitted. * The published install smoke installs both from their real feeds on its weekly run, driving the daemon as it does for Homebrew and Scoop, and resolving each package's declared dependencies because the documentation promises these channels install Node, git and `gh` for you. A version still in review is reported as a deliberate skip, timed from the submission rather than from the release so a repaired channel is not overdue the moment it is pushed, bounded at fourteen days — and never a skip once the queue has answered: a rejection, a version nobody submitted, or a wait whose length cannot be read are reported instead. * Chocolatey is asked through `choco search`, the interface Chocolatey documents as supported, and a search that fails is reported as a failure rather than read as an absent version. WinGet is asked of the client itself, because a merged manifest is not an indexed one. * WinGet submissions sync the fork before pushing, fetch the submission branch into its tracking ref, lease the value the run actually saw, do nothing for a version already merged, and warn when `WINGET_TOKEN` carries no `workflow` scope. Both WinGet jobs moved to Linux, where cloning a 689,147-file repository takes 1m24s rather than 16 minutes of a 30-minute budget. * The install catalog carries each channel's review queue and grace period, so the published note about these channels arriving later is checked against the code that decides it rather than kept by hand on the other side of a repository boundary. 0.5.9 was pushed to both feeds from `channel-republish.yml` before this branch was written: the Chocolatey submission is in moderation and microsoft/winget-pkgs#438396 is open.
Stephen Gillie (stephengillie)
approved these changes
Sep 21, 2026
Stephen Gillie (stephengillie)
added
the
Moderator-Approved
microsoft-github-policy-service
Bot
merged commit Sep 21, 2026
8024736
into
microsoft:master
130 checks passed
![microsoft-github-policy-service[bot]](https://avatars.githubusercontent.com/in/95686?s=60&v=4){kind=small}
Contributor
|
Validation has completed. Template: msftbot/validationCompleted |
Collaborator
|
Publish pipeline succeeded for this Pull Request. Once you refresh your index, this change should be present. |
microsoft-github-policy-service
Bot
added
the
Publish-Pipeline-Succeeded
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds LoopTroopAI.LoopTroop 0.5.9.
Manifests are generated from the release manifest by the same code that
renders this project's Homebrew, Scoop and Chocolatey descriptors, so the
installer URL and checksum come from one source of truth.
The installer is a portable executable in a zip; it carries its own Node
runtime, so only git is declared as a dependency.
Microsoft Reviewers: Open in CodeFlow