Support pre-releases such as 1.0.0-alpha1, 1.0.0-beta2, 1.0.0-rc5

[Ocramius]

Feature Request

See doctrine/automatic-releases#25

Currently the tool does not understand milestones named (\d+)\.(\d+)\.(\d+)\-(alpha|beta|rc)(\d*), nor knows how to sort them.

We want to support pre-release versions such as:

• 1.0.0-alpha1
• 1.0.0-beta32
• 1.0.0-rc99

This requires expansion of the SemVerVersion value object, but should otherwise operate as usual. The only tricky part is sorting versions.

Q	A
New Feature	yes
RFC	no
BC Break	no

[boesing]

We might consider semver v2 in general.

Semver v2 allows the following regex:
https://github.com/phly/keep-a-changelog/pull/72/files#diff-04b5d0b4bded820269443348d382fbc1R17

[Ocramius]

Makes sense.

@slash3b implemented similar parsing in https://github.com/Roave/SecurityAdvisoriesBuilder/blob/ffb14fc66d2534a1c2f36b98fb82951097aabe9c/src/Roave/SecurityAdvisories/Matchers.php#L31-L44

[boesing]

Yeah, the class also says "use semver regex from semver.org" :-D

^(?P<major>0|[1-9]\d*)\.(?P<minor>0|[1-9]\d*)\.(?P<patch>0|[1-9]\d*)(?:-(?P<prerelease>(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+(?P<buildmetadata>[0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$

This provides a good prerelease information which supposed to be all we need to see if we have to mark a release as pre-release or not:
https://regex101.com/r/Ly7O1x/3/

The only thing is, how can we provide patches with that.
I've seen several *p1 releases in laminas (due to failed migration from zend):
laminas/laminas-diactoros@2.2.1...2.2.1p1
Is that something we want to match aswell?