Edit in GitHubLog an issue

Versioning schema

Adobe Commerce and Magento Open Source application and module releases have their own unique version number.

Application version format#

A change in the version for the application indicates a patch or feature release. This version change does not reflect the nature of the changes in the code base.

Module version format#

The version field in a modules composer.json file specifies the module version and consists of three numbers in the following format:


The format follows Semantic Versioning rules for any @api annotated by code:

  • The MAJOR version increments when incompatible API changes are made.
  • The MINOR version increments when backward-compatible functionality has been added or if the module's customization points have changed.
  • The PATCH version increments when backward-compatible bug fixes occur.

Pre-release versions#

For pre-release versions, the format is:

MAJOR.MINOR.PATCH-<alpha | beta | rc>n

alpha, beta or rcStability indicators, as described in the version_compare() specification
nAn increment number to distinguish releases of the non-stable versions

Adobe's module versioning policy complies with the following specifications:

Where versioning is used#

The application version can be found in the source code of any component or bundle inside the composer.json file.

It can be declared as the version of the component:

Copied to your clipboard
1"name": "acme/foo",
2"version": 1.2.0

Or it can be used to declare a dependency on a particular version of a component:

Copied to your clipboard
1"require": {
2 "acme/foo": "1.2.*",
3 "acme/bar": "2.2.0"

Related topics:

Was this helpful?
  • Privacy
  • Terms of Use
  • Do not sell my personal information
  • AdChoices
Copyright © 2022 Adobe. All rights reserved.