The stable installer still installs server 2026.10.15, from before the 28 and 29 October security releases. This moves the dated line's pins forward, on a new release/2026 branch cut at v2026.10.15.2. Main stays on the 27.1 release candidates.
Pins
server 2026.10.29.1
console 2026.10.26.5
webmail 2026.10.26-gcff6f1f
Each checksum was copied from its release's SHA256SUMS and checked against fresh downloads for amd64 and arm64.
Also on the branch, cherry-picked from main:
Go 1.26.10 (GO-2026-6809)
the release-notes signature fix
release.yml now accepts tags on release/2026 as well as on main.
Checked: gofmt, vet for both architectures and go test ./.... The e2e cases install-local, install-host, upgrade-containers and upgrade-host-server (the upgrades from v2026.10.15.2) run before the tag.
Once this is merged, the tag is v2026.11.6.
The stable installer still installs server 2026.10.15, from before the 28 and 29 October security releases. This moves the dated line's pins forward, on a new `release/2026` branch cut at v2026.10.15.2. Main stays on the 27.1 release candidates.
**Pins**
- server 2026.10.29.1
- console 2026.10.26.5
- webmail 2026.10.26-gcff6f1f
Each checksum was copied from its release's SHA256SUMS and checked against fresh downloads for amd64 and arm64.
**Also on the branch**, cherry-picked from main:
- Go 1.26.10 (GO-2026-6809)
- the release-notes signature fix
**release.yml** now accepts tags on `release/2026` as well as on main.
**Checked:** gofmt, vet for both architectures and `go test ./...`. The e2e cases install-local, install-host, upgrade-containers and upgrade-host-server (the upgrades from v2026.10.15.2) run before the tag.
Once this is merged, the tag is v2026.11.6.
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.
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.
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.
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.
The stable installer still installs server 2026.10.15, from before the 28 and 29 October security releases. This moves the dated line's pins forward, on a new
release/2026branch cut at v2026.10.15.2. Main stays on the 27.1 release candidates.Pins
Each checksum was copied from its release's SHA256SUMS and checked against fresh downloads for amd64 and arm64.
Also on the branch, cherry-picked from main:
release.yml now accepts tags on
release/2026as well as on main.Checked: gofmt, vet for both architectures and
go test ./.... The e2e cases install-local, install-host, upgrade-containers and upgrade-host-server (the upgrades from v2026.10.15.2) run before the tag.Once this is merged, the tag is v2026.11.6.