jcoffey-dev is traveling from Thursday 1 October through Sunday 4 October. Issues and pull requests are welcome, and will get an answer after that. Thanks for your patience.
Re-release of 2026.9.30 with #136 (swap for the release link on GitHub runners). The v2026.9.30 tag build lost its arm64 image to an out-of-memory link, so it has no multi-arch index, GHCR copy, release binaries or announcement. The server code is unchanged from 2026.9.30.
Re-release of 2026.9.30 with #136 (swap for the release link on GitHub runners). The v2026.9.30 tag build lost its arm64 image to an out-of-memory link, so it has no multi-arch index, GHCR copy, release binaries or announcement. The server code is unchanged from 2026.9.30.
Landed with #138: that branch was cut from this one by mistake, so 1c1838a (Release 2026.9.30.1) reached main in 6c1eeea. Closing; nothing left to merge.
Landed with #138: that branch was cut from this one by mistake, so 1c1838a (Release 2026.9.30.1) reached main in 6c1eeea. Closing; nothing left to merge.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Re-release of 2026.9.30 with #136 (swap for the release link on GitHub runners). The v2026.9.30 tag build lost its arm64 image to an out-of-memory link, so it has no multi-arch index, GHCR copy, release binaries or announcement. The server code is unchanged from 2026.9.30.
Landed with #138: that branch was cut from this one by mistake, so
1c1838a(Release 2026.9.30.1) reached main in6c1eeea. Closing; nothing left to merge.Pull request closed