Magento software and Magento module releases have their own unique version number.
Software version format
A change in the version for the Magento software indicates a patch or feature release. This version change does not reflect the nature of the changes in the code base.
Module version format
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:
- The MAJOR version increments when incompatible API changes are made.
- The MINOR version increments when backward-compatible functionality has been added.
- The PATCH version increments when backward-compatible bug fixes occur.
For pre-release versions, the format is:
MAJOR.MINOR.PATCH-<alpha | beta | rc>n
||Stability indicators, as described in the
||An increment number to distinguish releases of the non-stable versions|
Magento’s module versioning policy complies with the following specifications:
Where versioning is used
The software version can be found in the source code of any Magento component
or bundle, inside the
It can be declared as the version of the component:
Or it can be used to declare a dependency on a particular version of a component:
If Magento is installed from GitHub without using Composer, the
version is not included. Magento Admin displays the version as
Magento ver. dev-<GitHub-branch-name>. In addition, Magento modules inside the
require declaration list a version of
*. For example,
Module version dependencies - Information about how your module can depend on the version of other modules.
Codebase changes - Information on how changes in a Magento module’s codebase affect versions.
Backward compatible development - Information about MAJOR and MINOR changes and how they impact extension developers.