-
Notifications
You must be signed in to change notification settings - Fork 15.1k
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
fix: Provide full and correct version in process.version
#11103
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree with the assessment of the problems and the goals of this patch, but have a couple of questions --
-
The semver spec is pretty clear this part of the name is called the 'pre-release version', perhaps we should reflect that here by using
ATOM_PRE_RELEASE_VERSION
instead ofATOM_LABEL_VERSION
-
Since this will be commented out for non-prerelease releases, we ought to have an #ifndef fallback just as we do with
ATOM_TAG
-
Related but perhaps out-of-scope for this patch, I'm not sure what role
ATOM_TAG
plays in this, it doesn't seem to be related to anything in semver. Is this a leftover from the old versioning scheme? If so, can we remove it safely? -
Also related but perhaps out-of-scope for this patch, it looks like non-releases would have a name something like
1.8.2-beta1-pre
which seems nonsensical. Does-pre
have some magic meaning that we're relying on in scripts somewhere?
@ckerr @vanessayuenn Good points!
As for dealing with downstream fallout, I believe we can rest easy - this change would only affect beta versions, while production versions will continue to report a "simple" version. |
Felix, IMO if Other than that, I'm fine with this patch |
@ckerr Updated once more! |
• Outputs the full and correct version from
process.version
• Updates the
bump_version.py
script to not break it in the futureCloses #11101