Adobe Commerce and Magento Open Source use semantic versioning on the individual module level (for example
magento/framework 101.1.1), but not for the marketing version number. For example:
The following guidelines apply to minor releases:
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:
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 proactively improve security 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.
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 Quick start install.
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 will have no obligation to maintain, correct, update, change, modify, or otherwise support (via Adobe Support Services or otherwise) the Beta Releases. Customers are advised to use caution and not to rely in any way on the correct functioning or performance of the Beta Releases and/or any accompanying documentation or materials. Accordingly, any use of the Beta Releases is entirely at Customer’s own risk.
Feature releases that contain new features and feature updates that are delivered as independent services, separate from patch releases. Examples include extensibility technology like API Mesh and Eventing, SaaS products like Product Recommendations and Live Search, independent modules like B2B and PWA Studio, and updates to our cloud hosting services and infrastructure.
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 for Adobe Commerce versions that are still supported and affected by critical security or quality issues, as needed. Hotfixes are published to the Known Issues section of our Knowledge Base. These fixes are included in the next planned patch release.
Hotfixes can contain backward incompatible changes.
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 our Software Lifecycle Policy.
Individual patches do not contain backward incompatible changes.
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.