OroCommerce Enterprise Edition releases
OroCommerce Enterprise Edition follows a structured release cycle with three types of releases:LTS (Long-Term Support)
Released once a year. Contains all features introduced in preview and patch releases since the previous LTS. Recommended for all production use.
Preview
Released a few months before the planned LTS. Contains new and potentially incomplete features for early compatibility testing. Not maintained — no patch releases.
Patch
Released as often as every few weeks for all active LTS versions. Used for bug fixes, security patches, and minor improvements.
Upgrade recommendations
For production environments, the most reliable upgrade path is to move from one LTS version to the next.| Version type | Recommended for | When to upgrade |
|---|---|---|
| LTS | All production users | Move from one LTS to the next for long-term stability. |
| Patch releases | All users on an active LTS version | Apply regularly to stay supported and up-to-date. |
| Preview versions | Enterprise partners and extension developers | Use to test extensions and customizations with upcoming features. |
Version numbering
OroCommerce uses a MAJOR.MINOR.PATCH version numbering scheme:- Major — Reserved for significant backward-incompatible architecture and technology changes, such as a switch to a new Symfony framework version.
- Minor — Introduces new features and provides a migration path for relatively small backward-incompatible changes.
- Patch — Usually contains no backward-incompatible changes unless explicitly stated in the release notes.
Release schedule
The Oro team works on a time-based schedule. A new LTS version is released every year in March, with multiple preview and patch versions published between LTS releases.LTS versions of OroCommerce Enterprise Edition are supported for 48 months from the release date. Oro’s Extended Coverage service can extend the lifespan by an additional 24 months, for a total of up to 6 years. Contact your Customer Success Manager for details.For versions released prior to 5.1 LTS, the standard support period is 36 months.
Enterprise Edition support timeline
| OroCommerce EE | Release date | Support ends | Extended coverage up to |
|---|---|---|---|
| 4.1 LTS | January 2020 | January 2023 | N/A |
| 4.2 LTS | January 2021 | January 2024 | December 2026 |
| 5.0 LTS | January 2022 | January 2025 | January 2028 |
| 5.1 LTS | March 2023 | March 2027 | March 2029 |
| 6.0 LTS | March 2024 | March 2028 | March 2030 |
| 6.1 LTS | March 2025 | March 2029 | March 2031 |
| 7.0 LTS | March 2026 | March 2030 | March 2032 |
New projects
If you are starting a new project, begin development on the most recent available patch version of the 6.1 LTS release.OroCommerce Community Edition releases
The Oro team produces patch releases for each version of OroCommerce Community Edition for 12 months after its release. Community developers and users have access to two product branches:- Stable — The 6.1 branch points to the latest stable release. Use this for testing and deployment. Upgrade to the next patch release tag as soon as it becomes available.
- Development — The 7.0 branch points to the latest published commit and is updated frequently. Only for developers and contributors actively following progress on GitHub. Not recommended for production.
Community Edition patch release availability
| OroCommerce CE | Release date | Patch releases available until |
|---|---|---|
| 5.0 | January 2022 | March 2023 |
| 5.1 | March 2023 | March 2024 |
| 6.0 | March 2024 | March 2025 |
| 6.1 | March 2025 | March 2026 |