-
-
Notifications
You must be signed in to change notification settings - Fork 649
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
[meta] Change git tagging pattern #579
Comments
Will change with the next release, thanks! |
It looks funny, because "nlohmann/json" had the opposite issue with Conan version ranges not working because of "v". |
as put by one of the commenters in the link:
😁 |
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
git-based package managers and tools often expect the repo tags for versions to be in the form of the version number prepended with "v" (as in
v1.2.3
) and there is an unwritten "rule" in GitHub that this is preferred way to tag versions.Using tags of this form will make the integration of doctest in such toolchains easier and make it more like many other GitHub projects.
The text was updated successfully, but these errors were encountered: