From 8538b8d5f6075ff3adf0c7124a5ff2c9fdd211ec Mon Sep 17 00:00:00 2001 From: Mikhail Yenuchenko Date: Tue, 18 Aug 2026 22:01:26 +0300 Subject: [PATCH] release: 1.5.0 Close Unreleased for send-log retention in Settings; pin compose and docs to 1.5.0. Co-authored-by: Cursor --- CHANGELOG.md | 5 +++++ README.md | 2 +- deploy/docker-compose.yml | 2 +- docs/development.md | 2 +- docs/guide.md | 4 ++-- docs/plans/send-log-retention.md | 4 ++-- docs/product.md | 8 ++++---- docs/roadmap.md | 30 +++++------------------------- 8 files changed, 21 insertions(+), 36 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 87a928f..59cdf45 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -5,6 +5,11 @@ Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); version ## [Unreleased] +## [1.5.0] - 2026-08-18 + +Send-log retention is configurable from panel **Settings** (global +administrator); `SEND_LOG_RETENTION_DAYS` seeds the initial default only. + ### Added - Panel **Settings** (global administrator): **Send log retention (days)** — diff --git a/README.md b/README.md index 17ab46c..e663afe 100644 --- a/README.md +++ b/README.md @@ -108,7 +108,7 @@ docker run --rm -d --name selfpost-try \ -e SELFPOST_HOSTNAME=mail.local.test \ -e PANEL_COOKIE_SECURE=false \ -v selfpost-try-data:/data \ - ghcr.io/mixeme/selfpost:1.4.0 + ghcr.io/mixeme/selfpost:1.5.0 ``` **Get the setup URL** (pick one): diff --git a/deploy/docker-compose.yml b/deploy/docker-compose.yml index e0f68c0..1f0a99f 100644 --- a/deploy/docker-compose.yml +++ b/deploy/docker-compose.yml @@ -22,7 +22,7 @@ services: selfpost: - image: ghcr.io/mixeme/selfpost:1.4.0 + image: ghcr.io/mixeme/selfpost:1.5.0 restart: unless-stopped environment: SELFPOST_HOSTNAME: "${SELFPOST_HOSTNAME:?set the mail/panel hostname, e.g. mail.example.com}" diff --git a/docs/development.md b/docs/development.md index f3e5d5a..65dca4f 100644 --- a/docs/development.md +++ b/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 | |---|---|---| diff --git a/docs/guide.md b/docs/guide.md index e6c1076..50baa0c 100644 --- a/docs/guide.md +++ b/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 diff --git a/docs/plans/send-log-retention.md b/docs/plans/send-log-retention.md index 30f2361..9493d5f 100644 --- a/docs/plans/send-log-retention.md +++ b/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). --- diff --git a/docs/product.md b/docs/product.md index 923c384..ac14bcc 100644 --- a/docs/product.md +++ b/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). --- diff --git a/docs/roadmap.md b/docs/roadmap.md index da33293..7e5a6cb 100644 --- a/docs/roadmap.md +++ b/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