Adobe Commerce release policy
- Topics:
- Release Notes
CREATED FOR:
- Experienced
- Admin
- Developer
Adobe Commerce uses semantic versioning on the individual module level (for example magento/framework 101.1.1), but not for the marketing version number. For example:
-
MAJOR release—2
-
MINOR release—2.4
-
PATCH release—2.4.8
-
SECURITY patch release—2.4.8-p1
- Security bug fix
- Security enhancement
-
-
ALPHA patch release—2.4.8-alpha1
-
BETA patch release—2.4.8-beta1
-
Extensibility, Infrastructure, and Services release
-
Hotfix
-
Individual patch
-
Custom patch
MINOR release
The following guidelines apply to minor releases:
- Breaking changes are possible; code written for Adobe Commerce 2.2.x may no longer work with Adobe Commerce 2.3.x. For example, minor releases can introduce support for major system requirements and dependencies, such as PHP.
- Module versions can vary. For example, some module changes are introduced in a new patch whereas others are introduced in a minor release.
- Minor releases can include new features that may require additional work by you or your solution partner during an upgrade to ensure compatibility.
- Minor releases can include fixes for security and quality issues.
PATCH release
Patch releases are primarily focused on delivering security, performance, compliance, and high-priority quality fixes to help you keep your sites performing at their peak.
The following guidelines apply to patch releases:
- The latest-supported minor release receives full functional quality fixes and enhancements.
- Changes that could break extensions or code compatibility are avoided. For example, code written for version 2.2.0 should still work on version 2.2.7.
- On an exceptional basis, breaking changes or additional patches or hotfixes may be released to address security or compliance issues and high-impact quality issues. On the module level, these changes are mostly PATCH-level; sometimes MINOR-level.
SECURITY patch release
Security Bug Fix: A software code change that resolves an identified security issue and delivers expected results in an affected product area. These fixes are generally backward compatible.
Security Enhancement: A software improvement or configuration change to improve security proactively within the application. These security enhancements help address security risks that impact the security posture of the Adobe Commerce application but may be backward incompatible.
With security patch releases, you can keep your site more secure without applying additional quality fixes and enhancements that are contained within a full patch release. Security patch releases are appended with ‘-pN’, where N is the incremental patch version beginning with 1 (for example, 2.3.5-p1). Security patch releases can also include hotfixes required to address critical issues that affect the Adobe Commerce application.
Security patch releases can also include compliance-related changes that are required to ensure that the Adobe Commerce application can meet compliance requirements. These changes may introduce backward-incompatible changes and are required to ensure that all supported release lines remain compliant.
Each security patch release is based on the prior full patch release. It contains quality and security fixes from prior patch release and security fixes created between the prior full patch release and the security patch release.
For instructions on downloading and applying security patches, see Peform and upgrade in the Upgrade Guide.
ALPHA patch release
Pre-Beta releases of Adobe Commerce features are made publicly available to all Adobe Commerce customers and Adobe partners. Alpha releases are intended for early feedback and evaluation of features that are still in active development. These releases provide an opportunity for early testing and integration planning ahead of Beta and General Availability releases.
Alpha releases may be incomplete, and are likely to contain defects. They are provided “AS IS” without warranty of any kind. Adobe has no obligation to maintain, correct, update, change, modify, or otherwise support (via Adobe Support Services or otherwise) Alpha releases. Customers should not rely on the correct functioning or performance of Alpha releases or any accompanying documentation or materials. Use of Alpha releases is entirely at the customer’s own risk.
BETA patch release
Pre-General Availability releases of Adobe Commerce features are made publicly available to all Adobe Commerce customers and Adobe partners. It allows for extra time before General Availability to review code and affected components.
Beta releases may contain defects and are provided “AS IS” without warranty of any kind. Adobe has no obligation to maintain, correct, update, change, modify, or otherwise support (via Adobe Support Services or otherwise) Beta releases. Customers should not rely on the correct functioning or performance of Beta releases or any accompanying documentation or materials. Accordingly, any use of the Beta Releases is entirely at a customer’s own risk.
Features, cloud infrastructure, and extensibility release
Cloud infrastructure and feature releases contain new features and feature updates that are delivered as independent services, separate from patch releases. Examples include, but are not limited to:
- Updates to cloud hosting services and infrastructure
- B2B
- SaaS products (Catalog Service, Data Connection, Product Recommendations, and Live Search)
- Extensibility technology (Admin UI SDK, API Mesh, App Builder Starter Kits, Eventing, and Webhooks)
Hotfix
Hotfixes are patches that contain high-impact security or quality fixes, such as fixes to zero-day vulnerabilities, that affect many merchants. Adobe releases hotfixes (as needed) for supported Adobe Commerce versions when critical security or quality issues affect them. Hotfixes are published to the Known Issues section of the Knowledge Base. These fixes are included in the next planned patch release.
NOTEIndividual patch
Individual patches contain low-impact quality fixes for a specific issue. These fixes are applied to the supported minor versions of Adobe Commerce. Adobe releases individual patches as needed for Adobe Commerce in accordance with the Software Lifecycle Policy.
NOTEIsolated patch
Isolated patchescContain a standalone fix that is included in the latest security-only patch or an upcoming security-only patch, which is being released separately for quicker implementation.
Custom patch
Created by non-Adobe personnel to fix an issue or modify the Adobe Commerce code for various reasons. Custom patches are delivered through the Quality Patches Tool.