Semantic versioning prerelease format
>>> [!note] Migrated issue
<!-- Drupal.org comment -->
<!-- Migrated from issue #3135897. -->
Reported by: [ccjjmartin](https://www.drupal.org/user/3210801)
>>>
<h2>Purpose</h2>
<p>Look at how prereleases are configured</p>
<h2>Background</h2>
<p>Current prereleases supported are alpha, beta, and rc: <a href="https://www.drupal.org/node/1015226#semver-transition">https://www.drupal.org/node/1015226#semver-transition</a></p>
<blockquote><p>{major}.{minor}.{patch}-(alpha|beta|rc){N}</p></blockquote>
<p>Currently when a prerelease is done a number is added at the end of the patch version, example: <code>beta1</code></p>
<h2>Request</h2>
<p>It would be more in line with semver(<a href="https://semver.org/#spec-item-9">https://semver.org/#spec-item-9</a>) to support prereleases formatted as <code>beta.1</code>, so the new format would look like <code>{major}.{minor}.{patch}-(alpha|beta|rc).{N}</code>with a dot between the prerelease type and the version identifier.</p>
<blockquote><p>A pre-release version MAY be denoted by appending a hyphen and a series of dot separated identifiers immediately following the patch version.</p></blockquote>
<blockquote><p>dot separated identifiers</p></blockquote>
<h2>Benefits</h2>
<p>This would open us up to potentially supporting other prerelease types and allow for quickly parsing releases by grabbing the version identifier after the dot.</p>
<h2>Practical example</h2>
<p>Specifically this would open up the community to using this tool for managing releases which has a whole ecosystem of supported integrations that allow for releases to be automatically done and published on different platforms via CI. Semantic release: <a href="https://github.com/semantic-release/semantic-release">https://github.com/semantic-release/semantic-release</a></p>
issue