-
Notifications
You must be signed in to change notification settings - Fork 3
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
Release v0.6 #89
Comments
For me I think it's good-to-go after #90 is sorted. |
It seems that the (edit: Zenodo) sandbox parent was nuked some time ago Maybe one can test against production Zenodo and just doesn't hit the button? |
Ran some quick tests with the rc .whl both with and without LiberTEM (py3.10 / ubuntu). All good for the full chain. I noticed that we don't have a convenience function that will run gridmatching on a frame or stack of frames, you're obliged to run the |
Implemented in #94 - once that is merged, I'll cut another RC |
rc2 is building here, let's specifically check the zenodo part: https://github.com/LiberTEM/LiberTEM-blobfinder/actions/runs/8720954308 |
RC2 looks good on Zenodo! |
I'll go ahead and tag v0.6.0 then! |
pypi upload is failing for some reason, I'll take care of it... |
Fixed by rotating credentials: https://pypi.org/project/libertem-blobfinder/ |
For some reason, the zenodo part now failed, see the log here: https://github.com/LiberTEM/LiberTEM-blobfinder/actions/runs/8721100857/job/23924930249 |
Hm, maybe because I had it open, or because it is irritated by the draft from the RC? Wasn't an issue before, so IDK, try again? |
GitHub release notes published here: https://github.com/LiberTEM/LiberTEM-blobfinder/releases/tag/v0.6.0 Changelog in the docs still needs to be consolidated.
Hm, can't easily re-run the job, as the zenodo upload comes after pypi, and pypi will complain loudly about the already existing release. Might need to run it carefully, manually (I don't have the credentials for that though). |
What about cutting 0.6.1, and if that shows the same issue I dig out the notebook to run this manually, with keys etc? |
Ok, I'll do that. |
Looks like that is needed. I think a good idea would be not to use the notebook, but the release script instead, so we are testing the thing that we are actually running in CI |
Manually it worked |
Still not there btw. - should check again tomorrow and maybe file a support issue with zenodo |
I'll manually contact the DOI people about the 404, and consider this done. |
Released on conda-forge (still waiting for CDN - can be confirmed with |
What's missing, anything TODO before we can cut a release?
TODO
The text was updated successfully, but these errors were encountered: