From 438819a94ae17350f0f6038822a828ed672d7662 Mon Sep 17 00:00:00 2001 From: autonomic-bot Date: Mon, 22 Jun 2026 21:44:13 +0000 Subject: [PATCH] =?UTF-8?q?upstream(mattermost-lts):=202026-06-22=20re-che?= =?UTF-8?q?ck=20=E2=80=94=2011.7.5=20still=20latest=20ESR?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- cc-ci-plan/upstream/mattermost-lts.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/cc-ci-plan/upstream/mattermost-lts.md b/cc-ci-plan/upstream/mattermost-lts.md index 16a9133..4489e80 100644 --- a/cc-ci-plan/upstream/mattermost-lts.md +++ b/cc-ci-plan/upstream/mattermost-lts.md @@ -16,6 +16,11 @@ The `release-11.7` Docker Hub floating tag always points to the latest 11.7.x patch. IMPORTANT: Do NOT use 11.7.0–11.7.2 — they have a schemeid migration bug in the `roles` table when upgrading from 10.11.17+; use 11.7.3 or later (current: 11.7.5). + - **2026-06-22 re-check** (endoflife.date/mattermost, data 2026-06-19): 11.7.5 is STILL the + newest 11.7.x patch (released 2026-06-18); 10.11 ESR security support ends 2026-08-15 + (~2 months); 10.12 innovation ENDED 2025-12-15 (do NOT target, despite abra listing 10.12.4); + 11.8 innovation EOL 2026-09-15. PR #2 (11.7.5 + restore fix) remains the correct, current + upgrade — this run is a confirmation re-verification, not a re-bump. - postgres: stay on **15-alpine** for now. The upgrade to 16-alpine requires a major-version migration (pg_upgrade or dump/restore with operator involvement) because the stack runs with a persistent postgres_data volume. A 16 container against pg15 PGDATA crashes on startup. Major pg bump is a