Installer v2026.10.12 went out still installing server 2026.10.10.1 and console 2026.10.5. Both had new releases that morning, and I didn't check before tagging. This PR is for v2026.10.12.1.
release.ServerVersion is now 2026.10.12, with the SHA-256 for both architectures taken from its SHA256SUMS. I checked both against downloads; both still need glibc 2.39.
The console image is now inbuxa-admin:2026.10.12. The webmail stays on 2026.10.9-g62936ab, still its newest release.
inbuxa:FrontEnds (server #195) missed 2026.10.12. So join's refusal of an older server, and the README, now say "newer than 2026.10.12".
The README's download example now names v2026.10.12.1.
Tests (fresh Debian 13 lab): install-local 26/26, install-host 43/43 (downloads and verifies the real 2026.10.12 binary), install-public 20/20, status-export 16/16, topology 28/28, and join 24/24 against a Debian 13 build of server main (9ce602c, which has #195). go vet and go test pass.
After merging: tag v2026.10.12.1, then merge docs inbuxa.org #73, which names that version.
Installer v2026.10.12 went out still installing server 2026.10.10.1 and console 2026.10.5. Both had new releases that morning, and I didn't check before tagging. This PR is for **v2026.10.12.1**.
- `release.ServerVersion` is now 2026.10.12, with the SHA-256 for both architectures taken from its SHA256SUMS. I checked both against downloads; both still need glibc 2.39.
- The console image is now `inbuxa-admin:2026.10.12`. The webmail stays on 2026.10.9-g62936ab, still its newest release.
- `inbuxa:FrontEnds` (server #195) missed 2026.10.12. So join's refusal of an older server, and the README, now say "newer than 2026.10.12".
- The README's download example now names v2026.10.12.1.
**Tests** (fresh Debian 13 lab): install-local 26/26, install-host 43/43 (downloads and verifies the real 2026.10.12 binary), install-public 20/20, status-export 16/16, topology 28/28, and join 24/24 against a Debian 13 build of server `main` (9ce602c, which has #195). `go vet` and `go test` pass.
After merging: tag v2026.10.12.1, then merge docs inbuxa.org #73, which names that version.
Server 2026.10.12 and console 2026.10.12 came out the morning installer
v2026.10.12 was tagged, which still installed server 2026.10.10.1 and
console 2026.10.5. The server's release binaries are pinned by checksum
again for --server host, copied from 2026.10.12's SHA256SUMS and checked
against downloads of both tarballs (both still need glibc 2.39). The
webmail's newest release is still 2026.10.9.
inbuxa:FrontEnds (server #195) missed 2026.10.12, so join's refusal of an
older server, and the README, now say it needs a release newer than that.
The README's download names v2026.10.12.1, the release this is for.
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.
Installer v2026.10.12 went out still installing server 2026.10.10.1 and console 2026.10.5. Both had new releases that morning, and I didn't check before tagging. This PR is for v2026.10.12.1.
release.ServerVersionis now 2026.10.12, with the SHA-256 for both architectures taken from its SHA256SUMS. I checked both against downloads; both still need glibc 2.39.inbuxa-admin:2026.10.12. The webmail stays on 2026.10.9-g62936ab, still its newest release.inbuxa:FrontEnds(server #195) missed 2026.10.12. So join's refusal of an older server, and the README, now say "newer than 2026.10.12".Tests (fresh Debian 13 lab): install-local 26/26, install-host 43/43 (downloads and verifies the real 2026.10.12 binary), install-public 20/20, status-export 16/16, topology 28/28, and join 24/24 against a Debian 13 build of server
main(9ce602c, which has #195).go vetandgo testpass.After merging: tag v2026.10.12.1, then merge docs inbuxa.org #73, which names that version.