Skip to main content
Version: Thelia 3

Release cycle and support

This page explains what a Thelia version number means, which series still receive fixes, how often releases have shipped so far, and how deprecations work. The disclosure policy and the table of supported series live in SECURITY.md in the core repository. If this page and that file differ, the file is right.

What a version number means​

The core follows semantic versioning. In 3.x.y:

  • a patch release (y) carries fixes only;
  • a minor release (x) adds features;
  • neither breaks code, templates or integrations written against an earlier 3.x release.

A breaking change ships in a major release only, after a deprecation period in the preceding minor releases. The surface covered by this promise, and what it leaves out, is listed in the backward compatibility promise. How a tag is chosen and branched is described in the Release Policy.

Modules and themes have their own version numbers. The back-office theme, for example, has a 1.x line while the core is in 3.x. A module declares the oldest core it works with in Config/module.xml, and that value is a minimum: a module that declares 3.0.0 keeps activating on a later 3.x core.

Supported series​

Only the two latest minor series are supported. The latest one gets every security fix, the one before it gets critical security fixes only, and a series reaches its end of support when the second minor release after it ships. Bug fixes that are not security fixes ship in the latest series only.

SeriesBranchSupportedEnd of support
3.43.4Yes, security fixesNone yet
3.33.3Critical security fixes only: update to 3.4With the 3.5.0 release
3.23.2No: update to 3.419 November 2026, with the 3.4.0 release
3.13.1No: update to 3.429 October 2026, with the 3.3.0 release
3.0NoneNo: update to 3.416 September 2026, with the 3.1.0 release
2.62.6No: update to 3.46 October 2026, with the 3.2.1 release
2.5 and olderNoneNoEnded

Thelia 3 is developed on a single trunk. A security fix ships in the next 3.x release, and a maintenance branch is only opened the day a fix has to ship without the changes waiting on main. Security fixes are therefore released for the latest 3.x versions only: keep your installation on the most recent release of its series.

To move a 2.6 shop to Thelia 3, follow Migrating from Thelia 2.

How often releases ship​

This is an observation, not a commitment. Releases are not tied to a calendar: the version number is decided from the content at tag time.

ReleaseDate
3.0.031 August 2026
3.1.016 September 2026
3.2.02 October 2026
3.3.029 October 2026
3.4.019 November 2026

Since 3.0.0, a new minor series has come out every two to four weeks. Patch releases come in between. Plan updates as a routine task rather than as a rare project: a series stops receiving fixes when the second minor release after it ships.

Deprecations​

Nothing covered by the compatibility promise is removed or changed without being deprecated first. The deprecation ships in a minor release, together with its replacement, and the old code keeps working. The removal happens in a major release, never in a minor or a patch one.

To see what is deprecated:

  • the CHANGELOG lists every deprecation and every behavior change under the version that introduces it;
  • the Breaking changes page lists, release by release, what a module or a theme has to change;
  • PHP code that uses a deprecated path triggers a deprecation notice, so a test run or a development environment shows it before an upgrade does.

The promise was written down in October 2026, during the 3.2 line. Code removed in 3.1.0 and 3.2.0 is listed in the Release Policy.

Every 3.x release updates a 3.0.0 shop in place. The procedure is on Update.