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
2 Commits
Author SHA1 Message Date
jcoffey-dev 3e2679206e 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
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.
2026-10-27 22:16:28 -07:00
jcoffey-dev 4f2a06ebbf 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
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.
2026-10-27 22:13:37 -07:00