Server 27.1-rc.4 → 27.1-rc.6, with both tarballs' checksums. rc.6 is rc.5 plus the fix for #265 (roles made in recovery mode before the first normal start), so this PR skips straight from rc.4 to rc.6. The first commit pinned rc.5, and the second moves it to rc.6.
Console 27.1-rc.3 → 27.1-rc.4, which pairs with the server: it has the Relays and Migrations pages.
RelaySHA256 gets the rc.6 relay binaries' checksums. Until now they were empty, so inbuxa relay install had no release to install.
Webmail stays on 27.1-rc.2.
Checks
Every checksum was copied from its release's SHA256SUMS and checked with sha256sum --check against the downloaded files.
Both relay .sig files verify with the CI release key. They name 27.1.0-rc.6 and the right target, and the x86_64 binary prints inbuxa-relay 27.1.0-rc.6. The relay and server images are published for amd64 and arm64.
A throwaway test (not committed) ran the installer's own path for every new pin: deps.FetchVerified with the pinned checksum, then relay.Verify with RelayKeys, RelayVersion() and RelayTarget() for both arches, plus the server and console tarballs. It passed.
gofmt, go vet (amd64 and arm64), and go test ./... pass; govulncheck finds no vulnerabilities (run on the first commit; the second only changes strings).
Next: an installer release candidate with these pins, when you want one.
- **Server 27.1-rc.4 → 27.1-rc.6**, with both tarballs' checksums. rc.6 is rc.5 plus the fix for #265 (roles made in recovery mode before the first normal start), so this PR skips straight from rc.4 to rc.6. The first commit pinned rc.5, and the second moves it to rc.6.
- **Console 27.1-rc.3 → 27.1-rc.4**, which pairs with the server: it has the Relays and Migrations pages.
- **`RelaySHA256`** gets the rc.6 relay binaries' checksums. Until now they were empty, so `inbuxa relay install` had no release to install.
Webmail stays on 27.1-rc.2.
## Checks
- Every checksum was copied from its release's SHA256SUMS and checked with `sha256sum --check` against the downloaded files.
- Both relay `.sig` files verify with the CI release key. They name `27.1.0-rc.6` and the right target, and the x86_64 binary prints `inbuxa-relay 27.1.0-rc.6`. The relay and server images are published for amd64 and arm64.
- A throwaway test (not committed) ran the installer's own path for every new pin: `deps.FetchVerified` with the pinned checksum, then `relay.Verify` with `RelayKeys`, `RelayVersion()` and `RelayTarget()` for both arches, plus the server and console tarballs. It passed.
- gofmt, `go vet` (amd64 and arm64), and `go test ./...` pass; govulncheck finds no vulnerabilities (run on the first commit; the second only changes strings).
Next: an installer release candidate with these pins, when you want one.
Server 27.1-rc.5 is the first release with inbuxa Relay, so `inbuxa
relay install` now has a relay to fetch: its binaries' checksums go in
RelaySHA256. Console 27.1-rc.4 pairs with it (the Relays and Migrations
pages).
Every checksum was copied from the release's SHA256SUMS and checked
against the downloaded files; both relay binaries' .sig files verify
with the CI release key, and name 27.1.0-rc.5 and their target.
27.1-rc.6 is rc.5 with the fix for roles made in recovery mode before
the first normal start (inbuxa-server #265), so the server and relay
checksums move to it. Console 27.1-rc.4 still pairs with it.
Checked as before: the release's SHA256SUMS against the downloaded
files, and both relay .sig files with the CI release key, naming
27.1.0-rc.6 and their targets.
jcoffey-dev
changed title from Install server 27.1-rc.5 and console 27.1-rc.4, and inbuxa Relay to Install server 27.1-rc.6 and console 27.1-rc.4, and inbuxa Relay2026-10-31 07:24:46 +00:00
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.
RelaySHA256gets the rc.6 relay binaries' checksums. Until now they were empty, soinbuxa relay installhad no release to install.Webmail stays on 27.1-rc.2.
Checks
sha256sum --checkagainst the downloaded files..sigfiles verify with the CI release key. They name27.1.0-rc.6and the right target, and the x86_64 binary printsinbuxa-relay 27.1.0-rc.6. The relay and server images are published for amd64 and arm64.deps.FetchVerifiedwith the pinned checksum, thenrelay.VerifywithRelayKeys,RelayVersion()andRelayTarget()for both arches, plus the server and console tarballs. It passed.go vet(amd64 and arm64), andgo test ./...pass; govulncheck finds no vulnerabilities (run on the first commit; the second only changes strings).Next: an installer release candidate with these pins, when you want one.
Install server 27.1-rc.5 and console 27.1-rc.4, and inbuxa Relayto Install server 27.1-rc.6 and console 27.1-rc.4, and inbuxa Relay