4 ms·
At least with Gitflow and Githubflow workflows, it is my understanding that we change the version number in the release/feature branch. With that understanding
by merlincorey 8y ago
At least with Gitflow and Githubflow workflows, it is my understanding that we change the version number in the release/feature branch.
With that understanding in mind (regardless of it matching your understanding, I mean), then clearly, "2.3.3-some.prerelease" is in fact less than "2.3.4", or it would have been named "2.3.4-some.prerelease".
Therefore, I believe it is clear that workflow must necessarily be considered to understand SemVer.
- munificent 8y agoSo if a user has the version constraint ">=2.3.3 <2.3.4", should they get that pre-release version?
- merlincorey 8y agoThis is covered explicitly in the SemVer specification section 11[0]. The answer depends on if there exists a released "2.3.3" version, in which case, the pre-release is not selected, because pre-release versions have less priority than release versions. The spec provides the following example: 1.0.0-alpha < 1.0.0-alpha.1 < 1.0.0-alpha.beta < 1.0.0-beta < 1.0.0-beta.2 < 1.0.0-beta.11 < 1.0.0-rc.1 < 1.0.0. [0] https://semver.org/#spec-item-11 https://semver.org/#spec-item-11