Skip to content

v0.5.3

Choose a tag to compare

View all tags
@github-actions github-actions released this 14 Aug 09:12
v0.5.3
6af38df
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

looptroop@0.5.3 release:notes
node scripts/print-release-notes.ts 0.5.3

  • Fixed an upgrade of the standalone executable that could leave LoopTroop stopped. If replacing the file failed, or the new version would not run, the old one was put back — but the daemon that had been stopped first was never started again, and the message said it was "back in place and working". Every path that stops the daemon now starts it again and says whether that worked.
  • Corrected the WinGet package to declare x64 rather than neutral. neutral means "runs on any architecture", which would have offered an Intel-only executable to Windows on ARM, where it is not built.
  • Paused publishing to Chocolatey, WinGet and the AUR. None of the three can currently complete — a moderation queue, a review queue, and a registration that is closed upstream — and a release job that cannot succeed teaches everyone to ignore a failed release. Each is one repository variable away from being switched back on.

Container image

docker pull looptroopai/looptroop:0.5.3
docker pull ghcr.io/looptroop-ai/looptroop:0.5.3

Both registries serve the same linux/amd64 + linux/arm64 index,
sha256:79faad8b8ea33b9292d0527a27631d6d59cdb6020bdb27a6a9233cb3e1f7316e.

The image ships without OpenCode, so a bare docker run exits at
startup by design — see Run it in a container
for how to point it at a server and reach the interface.

Assets 12
Loading