# Upstream sources — mattermost-lts

| service  | image                                     | source repo                                       | releases / changelog                                              |
|----------|-------------------------------------------|---------------------------------------------------|-------------------------------------------------------------------|
| app      | mattermost/mattermost-team-edition        | https://github.com/mattermost/mattermost          | https://docs.mattermost.com/about/mattermost-changelog.html       |
| postgres | postgres                                  | https://github.com/postgres/postgres              | https://www.postgresql.org/docs/release/                          |

## Standing notes
- mattermost-lts tracks the **11.7 ESR (Extended Support Release)**. Release calendar:
  - **10.11** = previous ESR, expires **2026-08-15** — migrated away 2026-06-19
  - **11.7** = current ESR, supported through **2027-05-15**; latest patch: **11.7.5** (2026-06-18)
  - **11.8.x** = innovation release (3-month lifecycle, EOL 2026-09-15) — do NOT target
  - **10.12** = innovation release, support **EXPIRED December 2025** — do NOT target
  - Check the release lifecycle at https://endoflife.date/mattermost before each upgrade run.
  - Next ESR after 11.7 expected ~February 2027 (9-month cadence)
  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
  separate operator-guided step.
- Backup format (as of PR #2 / upcoming 3.0.0+11.7.5 release): `pg_backup.sh` Docker config on the
  postgres service. Backup: `pg_dump | gzip → backup.sql`. Restore: terminate connections, FORCE-drop,
  recreate DB, reimport dump. `DROP DATABASE WITH (FORCE)` requires PostgreSQL 13+ — safe on postgres:15-alpine.
  The previous inline-label approach (no restore hook) was a defect: raw PGDATA restore without a reload
  was a silent no-op. Fixed in PR #2 (restore fix cherry-picked from PR #1 ci/pg-restore).