Outbound › Queue is the table the 2.0 mockup drew, and Inbound › Queue is built (6db3704, design629de5e, guards8525e8e, e2e853e0ca); the Overview card names both queues; TestUnbuiltScreensAreOnTheRoadmap keeps a deferred screen from being forgotten again. With it, two gaps the comparison of every mockup found (6edf831). No migration, schema 14. CHANGELOG section; pins in deploy/docker-compose.yml, README (build note) and the guide (pin, build, the backup example). No tag. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -5,6 +5,11 @@ Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); version
|
||||
|
||||
## [Unreleased]
|
||||
|
||||
## [2.16.0] - 2026-10-18
|
||||
|
||||
The queues as the 2.0 mockups drew them: Outbound › Queue a table, Inbound ›
|
||||
Queue built. No migration; schema 14.
|
||||
|
||||
### Added
|
||||
|
||||
- **Inbound › Queue** (`/inbound/queue`, global role, with the inbound relay
|
||||
|
||||
@@ -112,8 +112,8 @@ outbound mail will not reach the real internet without DNS, PTR, and port 25.
|
||||
> local image and pulls nothing:
|
||||
>
|
||||
> ```sh
|
||||
> docker build -f build/Dockerfile --build-arg VERSION=2.15.0 \
|
||||
> -t ghcr.io/mixeme/selfpost:2.15.0 .
|
||||
> docker build -f build/Dockerfile --build-arg VERSION=2.16.0 \
|
||||
> -t ghcr.io/mixeme/selfpost:2.16.0 .
|
||||
> ```
|
||||
|
||||
```sh
|
||||
@@ -122,7 +122,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:2.15.0
|
||||
ghcr.io/mixeme/selfpost:2.16.0
|
||||
```
|
||||
|
||||
This trial runs with Docker's default capabilities and no
|
||||
|
||||
@@ -23,7 +23,7 @@
|
||||
|
||||
services:
|
||||
selfpost:
|
||||
image: ghcr.io/mixeme/selfpost:2.15.0
|
||||
image: ghcr.io/mixeme/selfpost:2.16.0
|
||||
restart: unless-stopped
|
||||
environment:
|
||||
SELFPOST_HOSTNAME: "${SELFPOST_HOSTNAME:?set the mail/panel hostname, e.g. mail.example.com}"
|
||||
|
||||
+4
-4
@@ -218,14 +218,14 @@ 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 `2.15.0`. **No 2.x image is
|
||||
deliberately never `:latest`. The current pin is `2.16.0`. **No 2.x image is
|
||||
published on ghcr.io yet** (the newest there is `1.3.0`); until one is, build
|
||||
it from the checkout under the pinned name, and Compose uses the local image
|
||||
instead of pulling:
|
||||
|
||||
```sh
|
||||
docker build -f build/Dockerfile --build-arg VERSION=2.15.0 \
|
||||
-t ghcr.io/mixeme/selfpost:2.15.0 .
|
||||
docker build -f build/Dockerfile --build-arg VERSION=2.16.0 \
|
||||
-t ghcr.io/mixeme/selfpost:2.16.0 .
|
||||
```
|
||||
|
||||
`VERSION` must equal the tag: it is the version the backup check compares
|
||||
@@ -1084,7 +1084,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 2.14.5 but this image is 2.15.0 — restore into the matching image (selfpost:2.14.5)
|
||||
backup: this backup was created by SelfPost 2.15.0 but this image is 2.16.0 — restore into the matching image (selfpost:2.15.0)
|
||||
```
|
||||
|
||||
Fix the tag in `docker-compose.yml` (build that tag as under [Fixed image
|
||||
|
||||
Reference in New Issue
Block a user