This page has moved and will be redirected soon. See Migrated topics for the complete list.

Semantic Version Check


The Semantic Version Check (SVC) is a quality check that validates the change level of an extension submission against the change level declared by the extension developer.

What testing is for

Semantic Versioning is a good way to communicate what kind of changes were introduced between software releases. Clients can use this information to estimate the risk level of upgrading a particular software package and to determine how much effort is required to adopt the new version.

Magento follows Semantic Versioning and encourages all third-party vendors to apply this versioning strategy for their extensions as well.

Commerce Marketplace uses version information to fast-track the extension validation process for submissions that introduce patch level changes, as these are expected to be backwards compatible bug fixes without any new functionality.

When testing is done

For the Semantic Version check to be applied, the extension submission must meet the following conditions:

  1. A new submission must update an already existing version of an extension that has been previously published to the Marketplace storefront.
  2. The extension developer must declare the new submission as a “PATCH” level change.

What is being checked

The Semantic Version check analyzes the submission to determine the change level of the new submission and to verify whether the change level qualifies as a “PATCH” level change.

If the submission is a “PATCH” level change, the submission is fast-tracked and is exempt from the Manual QA process. Otherwise, this check fails.

A failed Semantic Version check has no impact on extension approval. If a submission receives Manual QA approval, then the extension will be published.

Tools and environments used

The Semantic Version Check is implemented using the publicly available, magento/magento-semver tool.

Magento SemVer is a static analysis tool that validates the change level of Magento source code based on the Semantic Versioning Specification and makes suggestions about the version increment to use, for example PATCH, MINOR, or MAJOR.

Magento SemVer can:

  1. Detect PATCH, MINOR and MAJOR change levels and suggest the appropriate change level for a new version.
  2. Validate an update against a desired change level.

Reading the error report

The error report lists minor and major changes detected in the extension source code. To fix an error, refactor the implementation until it no longer introduces non-patch level changes.


The Magento Semantic Version check uses the following command to check an extension:

php magento-semver/bin/svc compare <path-to-latest-published-extension-version> <path-to-submitted-extension-version> 1

This command requires an environment with PHP version 7.2.29 or later.

If the Semantic Version check detects any issues, create a support ticket to request assistance. Specify the relevant Submission ID in the ticket.

As the check is solely based on Magento SemVer open source project, submitting an issue or pull request on GitHub is highly recommended.

We always welcome feedback and discussion on the Magento Community Engineering Slack #marketplace channel.