-
Notifications
You must be signed in to change notification settings - Fork 44
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
pypi release github workflow failure #164
Comments
Ok, now I remember, it was this: pangeo-forge/pangeo-forge-recipes#127 (comment) Which we solved via:
I suspect that this related to the fact that we are still using versioneer for versioning. Versioneer is no longer maintained and we should probably switch to setuptools scm. |
I've never understood the niddy griddies of managing versions but in order to switch from versioneer, do I just uninstall it, delete versioneer.py and then follow the instructions for |
Yes, that sounds about right. You'll have to do some trial and error. It's probably going to be a pain in the neck. In both systems, the version is determined from the git tag, so when you're done with this refactor, the version number should not change. |
Alternatively, we could keep versioneer and you could look hard at the error message and try to understand what's going wrong. |
Considering that versioneer is no longer maintained (such a bummer), I think it would be wise to try to refactor xrft for setuptools_scm... I'll give a try. |
Cool. One thing you can do while debugging the CI is to make a bunch of "release candidate" (RC) releases, rather than continuing to bump the version. |
So now we are in the same place we were in with Pangeo Forge. setuptools-scm produces the correct version locally but the wrong one inside the github workflow. This is the same issue described in pangeo-forge/pangeo-forge-recipes#127 (comment). Hopefully it has the same fix. @TomAugspurger is the one who sorted it out there, but I wouldn't expect him to chime in here (very busy). Maybe we can retrace the steps he took by looking closely at pangeo-forge-recipes. |
Some breadcrumbs:
I think all of those were sufficient to fix the version issue. I don't recall what exactly was necessary. It might be worth checking if the |
https://github.com/xgcm/xrft/runs/3450436194?check_suite_focus=true
0%| | 0.00/31.4k [00:00<?, ?B/s]
26%|██▌ | 8.00k/31.4k [00:00<00:00, 60.3kB/s]
100%|██████████| 31.4k/31.4k [00:00<00:00, 81.7kB/s]
NOTE: Try --verbose to see response content.
HTTPError: 400 Bad Request from https://upload.pypi.org/legacy/
'0+untagged.0.g744209f' is an invalid value for Version. Error: Can't use PEP 440 local versions. See https://packaging.python.org/specifications/core-metadata for more information.
Error: Process completed with exit code 1.
The text was updated successfully, but these errors were encountered: