Install server 2026.10.29.1 on the stable line #47

Merged
jcoffey-dev merged 3 commits from pins/2026.10.29.1 into release/2026 2026-11-06 22:52:44 +00:00
3 Commits
Author SHA1 Message Date
jcoffey-dev 09cbf02ed9 Install server 2026.10.29.1, console 2026.10.26.5 and webmail 2026.10.26
ci / test (pull_request) Successful in 44s
The stable line's first release since 2026.10.15: the server's 28 and 29
October security releases, the console hotfix 2026.10.26.5, and the webmail
of 26 October. Checksums copied from each release's SHA256SUMS and checked
against freshly downloaded tarballs for both architectures.

Release tags may now sit on release/2026 as well as main: main installs the
27.1 release candidates, and the dated line keeps getting fixes from this
branch until 27.1 ships.
2026-11-06 15:40:14 -07:00
jcoffey-dev c46dc10d87 Keep the tag's SSH signature out of the release notes
The notes are the tag's message, and the step cut it off at a PGP
signature only. Tags are SSH-signed, so every release since then has
ended with the signature block. Any armored signature now ends the notes.
2026-11-06 15:37:36 -07:00
jcoffey-dev 45e5f0a2a2 Build with Go 1.26.10 (GO-2026-6809)
govulncheck fails CI on GO-2026-6809: crypto/x509 did not distrust some
compromised intermediate certificates before Go 1.26.10. The installer
reaches it through apply.ServedCertificate, which verifies the certificate
a server presents. The CI and release images move to the 1.26.10 digest,
and go.mod requires 1.26.10 so no older toolchain builds a release.
2026-11-06 15:37:36 -07:00