-
Notifications
You must be signed in to change notification settings - Fork 13
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 version names in docs #46
Comments
Seems like no initial tag was ever made. I would suggest
then
|
OK, thanks. I think we were at 1.1.8 on the old naming via the py files, so I'll start at 1.1.9. |
Hey @jGaboardi, the release build failed -- https://github.com/pysal/access/actions/runs/4683952297/jobs/8299566391 It seems like versioneer was set up for Is it as simple as find/replacing |
No, the failure is coming from the # get __version__
%run ../access/_version.py then add another cell __version__ = get_versions()["version"] |
Hey @jGaboardi, I noticed that we still have the weird versions in the docs -- I had pushed a tag long ago, and #47 fixed the other issue noted above. It looks like the docs build was 'fine" at that time -- https://github.com/pysal/access/actions/runs/4909247529 I just tried making a release from that v1.1.9 tag, but perhaps I need to do something else to trigger the build? I'm not familiar with versioneer or the current doc setup; do you have other ideas of what to check? |
I will give it attention over the weekend, if that's OK. Across the ecosystem we have been a bit fluid recently with adopting improved infrastructure. For example, swaping out |
xref #21 |
@jGaboardi, ever since the update to versioneer (#39), I noticed that the versions listed in the docs show up weird -- like
0+untagged.1.g109a527
:Could you either advise how to fix this with a new tag, or do so and mention me?
The text was updated successfully, but these errors were encountered: