Runtime
MariaDB
MariaDB 13.0, a non-LTS "rolling" release that shipped on 15 September 2026, reaches end of life on 31 December 2026 — roughly three and a half months of maintenance, after which the 13.0 series gets no further releases
departs 31 Dec 2026
Quick answers
- Is it true that MariaDB 13.0 reaches end of life on 31 December 2026 — a short-term rolling release, not an LTS?
- Yes. MariaDB has officially announced it, effective 31 Dec 2026. MariaDB 13.0 is a non-LTS release: it shipped on 15 September 2026 and its maintenance window ends on 31 December 2026, about three and a half months later.
- When does it take effect?
- 31 Dec 2026. Verified against the vendor's own announcement.
- What should I use instead?
- If you are running MariaDB 13.0, move to a long-term-support release rather than chasing the next short-term one.
What this means for you
MariaDB 13.0 is a non-LTS release: it shipped on 15 September 2026 and its maintenance window ends on 31 December 2026, about three and a half months later. That is by design — MariaDB now ships short-lived "rolling" releases between its long-term-support versions, and each one is superseded quickly. The trap is that a `.0` version number reads like a stable milestone when it is the opposite: after 31 December 2026 the 13.0 line receives no further maintenance releases, including security fixes. Anyone who pulled `mariadb:13` or `mariadb:13.0` into a Dockerfile, or installed 13.0 expecting normal support, is on a version that goes unmaintained at the end of the year. Production databases in particular should be on a MariaDB LTS release rather than a rolling one — the current LTS lines are 12.3 (supported to June 2029) and 11.8 (supported to June 2028).
Where to go
If you are running MariaDB 13.0, move to a long-term-support release rather than chasing the next short-term one. MariaDB 12.3 is the newest LTS, supported through 12 June 2029; 11.8 is an earlier LTS supported through 4 June 2028. Both receive maintenance and security updates for years rather than months. In Dockerfiles and compose files, replace `mariadb:13` / `mariadb:13.0` tags with a supported LTS tag such as `mariadb:12.3` or `mariadb:11.8`, and rehearse the upgrade on a copy — check for any changed defaults or deprecated settings between versions before cutting over production. If you specifically need a rolling release for testing new features, that is a legitimate use, but pin the expectation: it will fall out of maintenance within months and must be upgraded continuously.
- MariaDB 12.3 (LTS) — supported through 12 June 2029, the longest current runway
- MariaDB 11.8 (LTS) — supported through 4 June 2028
MariaDB 13.0 reaches end of life on 31 December 2026. The number is the story here: 13.0 shipped on 15 September 2026, so its entire maintenance window is about three and a half months. It is a non-LTS rolling release, not a long-term-support version.
MariaDB now ships short-lived rolling releases in between its LTS lines, and each one is superseded within a quarter or two. The hazard is that a .0 version reads like a stable, production-ready milestone when it is the opposite — a fast-moving release that goes unmaintained almost immediately. After 31 December 2026 the 13.0 series gets no further releases, including security fixes.
The exposure is anyone who reached for the newest number: an installation pinned to 13.0, or a container built on mariadb:13 / mariadb:13.0, expecting normal support. Production databases should be on an LTS line instead. The current long-term-support versions are MariaDB 12.3, supported through 12 June 2029, and 11.8, supported through 4 June 2028 — years of maintenance rather than months.
Moving is straightforward: bump mariadb:13 / mariadb:13.0 tags to mariadb:12.3 (or mariadb:11.8) in your Dockerfiles and compose files, rehearse the upgrade on a copy, and check for changed defaults between versions before cutting over. If you genuinely want a rolling release to test upcoming features, that’s fine — just treat it as continuously-upgraded, never as a version you can pin and forget.
Entry changelog
- — last reviewed.
- — Entry created from the MariaDB support-lifecycle data on endoflife.date, which records the 13.0 series (released 15 September 2026, latest 13.0.2) as a non-LTS release with an end-of-life date of 31 December 2026, alongside the current LTS lines 12.3 (EOL 12 June 2029) and 11.8 (EOL 4 June 2028). Date recorded exactly as listed. detect: fingerprints target the going-away `mariadb:13.0` / `mariadb:13` container tags only, never a supported LTS tag.
Put this countdown in your README
Building on MariaDB? Drop this badge into a project’s README or docs — it shows the days left and
refreshes on its own every night from this page. 
[](https://lastcall.dev/entries/mariadb-13-0-end-of-life)Spot an error or a changed date? Tell us and it’s corrected the same night.