-
Notifications
You must be signed in to change notification settings - Fork 686
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question: Prerelease and release number must be the same for same code? #841
Comments
I think you're misusing semvar in this situation. It's designed to version packages that are released for use whether that be npm, cargo or any other form of release. In general, git branches aren't releases of the package because they don't represent a specific version of the code but a series of changes. So if you have a branch In general, I would recommend that only master have a version (and a tag on a specific commit to specify that version) as usually in spirit with git flow. |
This comment was marked as off-topic.
This comment was marked as off-topic.
Version tags on git content hashes are redundant and don't scale well. The purpose of release branches however is to provide an easy point to go back to when you need to roll a fix across multiple releases. You don't generally create them for minor, patch or prerelease changes, you create them when you must support several major versions at one time, so the nomenclature should be more like v1, v2, v3 (non semver tags) for your release branches. In other words, you don't apply SemVer to your source. Instead you go back and tag the content hash that produced whatever bits you finally released, which is something that happens after the build is completed and asynchronous to any source code changes taking place. |
In a project I use gitflow and semver in this way:
Of course the prereleases has much more new versions that the develop and the main.
With this situation:
1.0.0
1.0.1-beta, 1.0.2-beta
1.0.1-alpha, 1.0.2-alpha, ... 1.0.12-alpha
if I merge 1.0.12-alpha on develop ewhat is the right new beta version?
same question for "release" version.
The text was updated successfully, but these errors were encountered: