release: 1.5.0

Close Unreleased for send-log retention in Settings; pin compose and docs to 1.5.0.

Co-authored-by: Cursor <cursoragent@cursor.com>

docs/development.md

@@ -102,7 +102,7 @@ than the default «meaningful step» rule in [§ Commits and release build](#com
 2. Git tag `vX.Y.Z` and publish the GitHub Release only on explicit request (see
    [§ Release image](#release-image)).
 
-**Planned version cuts** (from pin `1.4.0`; adjust if semver changes mid-track):
+**Planned version cuts** (from pin `1.5.0`; adjust if semver changes mid-track):
 
 | Stage | ID | Cut |
 |---|---|---|

docs/guide.md

@@ -169,7 +169,7 @@ cat ./data/setup-token
 #### Fixed image tag
 
 `deploy/docker-compose.yml` pins an explicit version (`ghcr.io/mixeme/selfpost:X.Y.Z`),
-deliberately never `:latest`. The current pin is `1.4.0`. Intermediate
+deliberately never `:latest`. The current pin is `1.5.0`. Intermediate
 CHANGELOG sections (`0.2.0`…`0.6.0`) record development cuts from before that
 image was published. Pinning matters because of the backup version check (see
 [Full backup and restore](#full-backup-and-restore)): the panel binary's
@@ -491,7 +491,7 @@ A version mismatch at step 5 refuses to start and leaves `/data` untouched —
 the panel exits with a message naming the tag to use, e.g.:
 
 ```
-backup: this backup was created by SelfPost 1.2.3 but this image is 1.4.0 — restore into the matching image (selfpost:1.2.3)
+backup: this backup was created by SelfPost 1.2.3 but this image is 1.5.0 — restore into the matching image (selfpost:1.2.3)
 ```
 
 Fix the tag in `docker-compose.yml`, `docker compose pull && docker compose up

docs/plans/send-log-retention.md

@@ -1,8 +1,8 @@
 # Plan: send-log-retention
 
-**Status:** done  
+**Status:** done — shipped in `[1.5.0]` (2026-08-18)  
 **Date:** 2026-08-17  
-**Version:** `1.x` MINOR; no schema migration required (uses existing `settings` table).
+**Version:** `1.5.0` MINOR; no schema migration required (uses existing `settings` table).
 
 ---
 

docs/product.md

@@ -58,11 +58,11 @@ Explicitly excluded to prevent scope creep:
 The **domain-admin** role ships in the current line (global administrator plus
 domain administrators with assigned domains). The optional **inbound relay**
 (backup-MX / forwarder on port 25) ships in `[1.4.0]`, off by default behind
-`INBOUND_RELAY_ENABLE`; it is relay/forward, not IMAP/webmail. Items
-marked *candidate* in the
+`INBOUND_RELAY_ENABLE`; it is relay/forward, not IMAP/webmail. **Send-log
+retention in Settings** ships in `[1.5.0]`. Items marked *candidate* in the
 [roadmap](roadmap.md) require explicit approval before coding (including
-**send-log retention in Settings**, **30-day send statistics**, and **auto
-level-2 rate limits** — see linked plans there).
+**30-day send statistics** and **auto level-2 rate limits** — see linked
+plans there).
 
 ---
 

docs/roadmap.md

@@ -28,7 +28,6 @@ in `git log` and [CHANGELOG.md](../CHANGELOG.md).
 
 | ID | Topic | Status | Progress | Plan |
 |---|---|---|---|---|
-| send-log-retention | Send-log retention days in panel Settings | done | 8/8 | [plans/send-log-retention.md](plans/send-log-retention.md) |
 | domain-stats-auto-ratelimit | 30-day send stats + auto level-2 rate limit | candidate | 0/11 | [plans/domain-stats-auto-ratelimit.md](plans/domain-stats-auto-ratelimit.md) |
 | contributing | `CONTRIBUTING.md` | candidate | — | — |
 | dmarc-reports | DMARC aggregate report ingestion and panel UI | candidate | 0/8 | [plans/dmarc-reports.md](plans/dmarc-reports.md) |
@@ -36,12 +35,11 @@ in `git log` and [CHANGELOG.md](../CHANGELOG.md).
 | schema-squash | Squash SQLite migrations into a 2.x baseline | **2.x** | — | — |
 
 **Recommended order** (not binding): the next feature is
-**send-log-retention** once agreed. It can land before or beside
-**domain-stats-auto-ratelimit** (panel retention ≥ 30 days helps the stats
-window). inbound-relay shipped in
-[CHANGELOG.md](../CHANGELOG.md) `[1.4.0]`; queue-retries in `[1.3.1]`; the
-2026-08-13 full-tree review follow-ups are in `[1.3.0]`. Candidates need
-explicit agreement before they join the queue.
+**domain-stats-auto-ratelimit** once agreed (panel retention ≥ 30 days helps
+the stats window). send-log-retention shipped in
+[CHANGELOG.md](../CHANGELOG.md) `[1.5.0]`; inbound-relay in `[1.4.0]`;
+queue-retries in `[1.3.1]`; the 2026-08-13 full-tree review follow-ups are in
+`[1.3.0]`. Candidates need explicit agreement before they join the queue.
 
 After a context reset, pick an item marked `agreed` or `in progress`, then work
 the **Implementation checklist** in its linked plan. The `Progress` column above
@@ -50,24 +48,6 @@ is `done/total` checklist steps in that plan ([development.md](development.md)
 
 ---
 
-## send-log-retention
-
-**Goal:** global administrator sets how many days of delivery journal rows
-(`send_log`, `/deliveries`) are kept, from `/settings` — stored in SQLite
-`settings`, with `SEND_LOG_RETENTION_DAYS` as bootstrap default only.
-
-**Boundary:** instance-wide retention; not per-domain. Does not change
-`mail.log` rotation. Today retention is env-only (default 90 days); the panel
-has no control.
-
-**Done when:** see [plans/send-log-retention.md](plans/send-log-retention.md).
-
-**Dependencies / risks:** log-tailer must re-read settings each prune cycle;
-delivery UI must stop hardcoding «ninety days».
-**Version:** `1.x` MINOR; `candidate` until explicitly agreed.
-
----
-
 ## domain-stats-auto-ratelimit
 
 **Goal:** 30-day sending statistics per domain and application (total, peak and