-
Notifications
You must be signed in to change notification settings - Fork 359
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
micromamba/mamba --version
displays pre-release version names + establishes pre-release versions name scheme
#3639
base: main
Are you sure you want to change the base?
Conversation
d130b82
to
b618cb7
Compare
Note that this version accepts a minimum of 3 dot-separated fields but does not limit the number of dots over 3, so schemes with and without additional dots are considered "valid" by the validation script. |
version_scheme.py
Outdated
) | ||
) | ||
|
||
VALID_VERSION_PRERELEASE_TYPES = ("alpha", "beta") |
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.
What about rc
and dev
?
Adding this as a reference. |
This piece of |
2ac4450
to
08aa760
Compare
…d and make that field visible in `--version`
08aa760
to
75c1a46
Compare
Part of the effort for #3638
While I started this just to allow displaying the pre-release versions in
micromamba/mamba --version
, this required also changing the release scripts to provide the relevant information to the source code. As part of that change I setup the discussed pre-release version naming scheme with validation in the release scripts.Also deprecates
mamba::version_arr()
andumamba::version_arr()
functions which seem unusued. If there is a need for information about the version, I'll add another more precise function as a replacement, or we'll just remove these.