-
Notifications
You must be signed in to change notification settings - Fork 2
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
Version number does not display properly on ReadTheDocs #99
Comments
Not sure if this is related or not… but
|
Ooh good catch, yeah that does make sense. I don't remember offhand if setuptools-scm relies on If that's the case, then we might have to switch things around so that we manually create (annotated) tags, or at least create them in CI with a |
I'm a bit surprised that Github doesn't create annotated tags actually. |
Yeah same, or at least that it doesn't offer the option to do so. |
I found a Stack Overflow question about this with some ideas to try. The ReadTheDocs documentation does call out having to work around a dirty Git working tree, so that's one thing to try, but I'm not sure if that will be enough. |
Yep, they also mention that RTD does sometimes manipulate files… https://stackoverflow.com/questions/35811267/readthedocs-and-setuptools-scm-version-wrong/41949974#41949974 in particular, suggests installing the module then reading out the version number directly. |
In the documentation for our stable release 0.1, the version number at the top left is displayed as "setuptools-pyproject-migration 0.1.1.dev0+gfde5f75.d20231010". We need to fix that so it displays properly, e.g. for this release it should show
0.1
, or for future releases something like0.1.post0
or0.1.1
or0.2
or whatever.The text was updated successfully, but these errors were encountered: