Deploy Stalwart 0.16.27 by default, and say what is supported #22

Merged
jcoffey-dev merged 2 commits from support/stalwart-0-16-27 into main 2026-10-28 06:35:35 +00:00
Owner
  • Default Stalwart image: v0.16.22 → v0.16.27, the last 0.16 release and the one ihasmail now tests against (coffey-labs/ihasmail#65).
    • --local deploy against 0.16.27: set up Stalwart, created a mailbox, signed in to ihasmail 2026.10.27.
    • Public-mode end-to-end test passed, 20/20 checks (e2e job on a GitHub runner, run by hand on this branch): certificates on 993/465/443 from Pebble, alice signs in through the webmail, autoconfig, the auto-ban hits the scanner and not Caddy, ihasmail exempt.
  • README: a Support section. 0.16.27 is supported and the default. Other 0.16 releases are untested. 1.0 isn't supported, because its first-run setup changed. Troubleshooting's known limits say the same.
  • README and CONTRIBUTING said the end-to-end test runs every Monday. Since the move to Gitea it has been a job run by hand on a GitHub runner, so they say that now.
  • Go 1.26.10 for GO-2026-6809 (crypto/x509). The first CI run on this branch failed govulncheck on 1.26.9. go.mod and the Gitea CI image now match stalwart-migrator's #22. The current release binary is built with 1.26.9, so a release after merging picks up the fix too.

Ran locally: go vet ./..., go test ./..., govulncheck with Go 1.26.10 (no vulnerabilities).

- **Default Stalwart image: v0.16.22 → v0.16.27**, the last 0.16 release and the one ihasmail now tests against (coffey-labs/ihasmail#65). - `--local` deploy against 0.16.27: set up Stalwart, created a mailbox, signed in to ihasmail 2026.10.27. - **Public-mode end-to-end test passed, 20/20 checks** (`e2e` job on a GitHub runner, run by hand on this branch): certificates on 993/465/443 from Pebble, alice signs in through the webmail, autoconfig, the auto-ban hits the scanner and not Caddy, ihasmail exempt. - **README: a Support section.** 0.16.27 is supported and the default. Other 0.16 releases are untested. 1.0 isn't supported, because its first-run setup changed. Troubleshooting's known limits say the same. - **README and CONTRIBUTING** said the end-to-end test runs every Monday. Since the move to Gitea it has been a job run by hand on a GitHub runner, so they say that now. - **Go 1.26.10 for GO-2026-6809** (crypto/x509). The first CI run on this branch failed govulncheck on 1.26.9. go.mod and the Gitea CI image now match stalwart-migrator's #22. The current release binary is built with 1.26.9, so a release after merging picks up the fix too. Ran locally: `go vet ./...`, `go test ./...`, `govulncheck` with Go 1.26.10 (no vulnerabilities).
jcoffey-dev added 1 commit 2026-10-28 05:14:31 +00:00
Deploy Stalwart 0.16.27 by default, and say what is supported
ci / test (pull_request) Skipped
ci / release (pull_request) Skipped
github/ci (branch) GitHub Actions
ci / github (pull_request) Failing after 1m12s
ci / announce (pull_request) Skipped
4f2a06ebbf
The default Stalwart image moves from v0.16.22 to v0.16.27, the last 0.16
release and the one ihasmail now tests against. A loopback deploy
(--local) against it set up Stalwart, created a mailbox and signed in to
ihasmail 2026.10.27.

The README gets a Support section: 0.16.27 supported and the default, other
0.16 releases untested, 1.0 not supported because its first-run setup
changed. Troubleshooting's known limits say the same.

The README and CONTRIBUTING said the end-to-end test runs every Monday. It
has been a job run by hand on a GitHub runner since the move to Gitea.
jcoffey-dev added 1 commit 2026-10-28 05:16:31 +00:00
Build with Go 1.26.10 for GO-2026-6809
ci / test (pull_request) Skipped
ci / release (pull_request) Skipped
github/ci (branch) GitHub Actions
ci / github (pull_request) Successful in 2m11s
ci / announce (pull_request) Skipped
3e2679206e
govulncheck on GitHub's runner (GOTOOLCHAIN=local, Go from go.mod) reports
GO-2026-6809 in crypto/x509 on 1.26.9, reachable from main. go.mod moves to
1.26.10 and the Gitea CI image to the 1.26-bookworm digest that ships it, the
same bump stalwart-migrator made in its #22.
jcoffey-dev merged commit b3f7981acd into main 2026-10-28 06:35:35 +00:00
jcoffey-dev deleted branch support/stalwart-0-16-27 2026-10-28 06:35:35 +00:00
Sign in to join this conversation.