deniz.in

Markets

Weather

Loading weather

· via dev.to (home feed)

MariaDB's post-2024 release model leaves 10.6 unsupported and 11.4 outliving 11.8

A dev.to guide maps MariaDB's post-2024 support timelines: 10.6 is already end-of-life, 11.4 outlives 11.8, and admins should pick an LTS with 18 months of support left.

MariaDB's post-2024 release model leaves 10.6 unsupported and 11.4 outliving 11.8

MariaDB's 2024 overhaul of its release model has settled into a rhythm that rewards planning over habit: short-lived rolling releases each year, plus a single long-term-support version backed for three years rather than five. According to a guide published on dev.to by srvScripts, version choice has become a policy decision for server administrators, and some old assumptions — such as a newer LTS always outliving an older one — no longer hold.

How the release model works

Each yearly MariaDB series now ships four minor versions, srvScripts explains. The .0, .1 and .2 releases are rolling: they receive support only until the next one arrives and are aimed at early adopters and testing. The .3 release of each series is the LTS, backed for three years. That makes 12.0, 12.1 and 12.2 short-lived intermediates, while 12.3, released on 28 May 2026, is the production candidate. The same cycle is repeating with 13.0, released on 15 September 2026, which precedes a 13.3 LTS expected around mid-2027. Rolling releases belong on a staging box, the guide argues, not on a customer-facing server.

Where each version stands

As of late September 2026, the guide lists the following positions. MariaDB 10.6 reached end of life on 6 July 2026, its final release being 10.6.28, and is unsupported. 10.11 LTS runs until February 2028 (currently 10.11.19) and remains cPanel's default for new installs. 11.4 LTS is supported until May 2029 (currently 11.4.13), 11.8 LTS until June 2028 (11.8.9), and 12.3 LTS until June 2029 (12.3.3). Quarterly maintenance releases landed across every supported series on 24 August 2026.

The counterintuitive entry is 11.4 outliving 11.8 by nearly a year, an artifact of how the LTS windows were set at different points during the transition. srvScripts frames this as a trade-off: 11.4 offers the longest support remaining within the 11.x line, while 11.8 is the last 11.x LTS to carry newer features such as VECTOR, the VEC_DISTANCE functions and improved JSON handling.

What the control panels offer

Panel support constrains what administrators can deploy. On cPanel, the WHM upgrade workflow offers MariaDB 10.5 through 11.8 on AlmaLinux 8 and 9, narrows to 10.11, 11.4 and 11.8 on AlmaLinux 10, and spans 10.6 through 11.8 on Ubuntu 24.04. Version 12.3 is not yet available in WHM, and new cPanel installs default to 10.11. DirectAdmin's CustomBuild tracks 10.6, 10.11, 11.4, 11.8 and 12.3 alongside MySQL 8.0 and 8.4, having dropped MySQL 5.7 and MariaDB 10.3 in release 1.693, and it expects upgrades to step through LTS versions in order rather than skipping. Standalone servers using the upstream repository can run anything on the list.

An eighteen-month rule for the fleet

srvScripts reduces the policy to a single rule: run an LTS with at least eighteen months of support remaining. Applied to the current timeline, a server still on 10.6 is overdue and should move now — to 11.8 under cPanel, or 12.3 on DirectAdmin and standalone — following the documented upgrade paths. A server on 10.11 is not urgent, since February 2028 has only just entered the eighteen-month window, but its move should be scheduled for the first half of 2027. Servers on 11.4 or 12.3 need no action until planning for 2028. The 11.8 fleet is safe for now, but because its June 2028 cutoff precedes 11.4's, those servers should shift to 12.3 or the future 13.3 in early 2027. For new builds, the guide recommends 11.8 on cPanel until WHM gains 12.3 support, and 12.3 everywhere else.

The maintenance-release trap

The guide also flags a common mistake: reading a version such as 12.3.3 as a minor point release that can wait. Within an LTS series the third number is the maintenance release, and that is where security fixes land — a server still on 12.3.0 is missing every fix since May. srvScripts advises keeping patch levels current through the ordinary update channel, whether that is cPanel's update tooling, DirectAdmin's build commands or the package manager on standalone servers, with any restart done in a maintenance window. It also suggests a quarterly fleet-wide version check, with database end-of-life dates tracked in the same calendar or monitoring system used for certificate and operating-system expiry.

Why it matters

The pre-2024 model let hosting providers treat a MariaDB major version as a five-year commitment. That margin is gone: rolling releases are not production-safe, LTS support lasts three years, and the transition left quirks such as 11.4 outliving 11.8 that will catch anyone choosing by version number alone. With 10.6 already end-of-life and 10.11 inside the eighteen-month window, administrators who have not revisited their database version policy since the change are the ones now short on time — and the security-relevant fixes sit in easily overlooked patch releases. Mapping every server against its remaining support window, and provisioning new builds with the longest-lived LTS the panel allows, turns an ambiguous release model back into a manageable schedule.

  • #mariadb
  • #databases
  • #lts
  • #server-administration
  • #web-hosting