Releases made for contributed projects on Drupal.org must follow specific version number formatting requirements. Currently this is {API compatibility}-{major}.{minor}[-(alpha|beta|RC){number}]
. Future releases are allowed to use semantic versioning, {major}.{minor}.{patch}[-(alpha|beta|RC){number}]
, dropping the API compatibility component and adding a patch component.
Drupal.org’s Composer endpoint reformats legacy version numbers to semantic versioning, the patch component is always 0
. Semantic-versioned releases will go into the 8.x
composer endpoint, so Drupal 8, 9, and later sites may install them. There will be restrictions on version numbering to avoid conflicts; for example, if a project has 8.x-1.0
released, they will not be able to release 1.0.0
too.
See documentation on Release naming conventions for information on how to use Semantic Versioning for projects on Drupal.org.
Examples of valid semver versions (branches):
1.0.x, 1.1.x, 2.0.x, 1.x, 2.x, etc.
Comments
Updates API XML
Note that the updates API XML endpoint from drupal.org will not reply with semantic-versioned releases when you query for the 8.x compatibility level. You must use "current" to retrieve 8.x+ projects.