Announcement: You can find the guides for Commerce 7.5 and later on the new Elastic Path Documentation site. This Developer Center contains the guides for Commerce 6.13.0 through 7.4.1.Visit new site

This version of Elastic Path Commerce is no longer supported or maintained. To upgrade to the latest version, contact your Elastic Path representative.

Version Number Conventions

Version Number Conventions

The following conventions are recommended for versioning customer projects:

Best practices

Do not reversion development branch on each release

  • Updating the development branch version number on each release is additional work, adds noise to the commit history, and provides marginal value.
  • It is more effective to update version number only on release branches and to use the same development version throughout the project.

Update versions numbers only on the release branch

  • Update versions numbers on the release branch immediately after it is created. This will distinguish release artifacts from development artifacts.
  • Do not merge version number changes back into development.