From 2d75cbe39f1652a6d1698b08808b17490ec09c3e Mon Sep 17 00:00:00 2001 From: MarekWo Date: Sat, 12 Sep 2026 18:20:09 +0200 Subject: [PATCH] chore(release): finalize 2.18.2 Co-Authored-By: Claude Opus 5 --- VERSION | 2 +- docs/whatsnew.md | 4 ++++ 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/VERSION b/VERSION index 4a47f85..e9187f6 100644 --- a/VERSION +++ b/VERSION @@ -1 +1 @@ -2.19.0-dev \ No newline at end of file +2.18.2 \ No newline at end of file diff --git a/docs/whatsnew.md b/docs/whatsnew.md index 625a3b4..2bf57f8 100644 --- a/docs/whatsnew.md +++ b/docs/whatsnew.md @@ -10,6 +10,10 @@ For deep technical notes, see [architecture.md](architecture.md). For the full g ## Unreleased +--- + +## 2.18.2 — 2026-09-12 + ### Fixes - **Optional HTTPS now works on installations made from the Docker image, not only on those built from source.** mc-webui can be installed two ways, and they differ in one detail that turned out to matter: an installation built from the repository uses the `docker-compose.yml` that comes with it, while an installation from the published Docker image uses a `docker-compose.yml` that the README told you to write yourself. The optional HTTPS proxy ([HTTPS Setup](https-setup.md)) is defined in the project's file behind a Compose *profile*, so adding `COMPOSE_PROFILES=https` to `.env` starts it — but a hand-written file never had that definition, so the same line did nothing at all: the app started as before and no proxy was mentioned, with no error to explain why. Pasting the proxy into the file by hand worked, and then had to be redone by hand every time anything else was added to it. The same gap silently swallowed `MC_TRUST_PROXY` and `MC_BIND_ADDRESS` — the two settings that let the app see the real client address and close the plain-HTTP port — because those are passed to the app by the compose file too.