zenodo is stuck at 1.2.0

[fkiraly]

I believe the zenodo got unlinked from the repository at some point, it points at version 1.2.0 (from 2022) currently:
https://zenodo.org/records/5818272

To fix this, I believe one of the repo owners has to log in to zenodo and link the repo back.

[solegalli]

Just checked the link and it seems to be working.

[fkiraly]

Ok, this is strange that it works for you but not for me.
This is what I get when following the link, version 1.2.0:

[solegalli]

I understand the issue now. I believe it is due to me not making releases on github whenever I make a release on pypi/conda. The last one was 1.2

[fkiraly]

oh, you are not releasing on GitHub? Do you want a GHA workflow for that maybe?

It is pretty convenient!

[solegalli]

Yes, that would be great.

Just for clarification, we release to pypi based on branch name using a circleci workflow.

This would be to make a release on github only, right?

[fkiraly]

This would be to make a release on github only, right?

Well, if you use GHA, you can add trigger conditions so that the release on GitHub also triggers the release on pypi, so it is a single button press.

That circle ci does this for you is a complication - as said elsewhere, I am not familiar with circle CI, so I would not exactly know what I am doing unless I read up on it.

However, I can explain how a GHA trigger would looke like, e.g., in a draft PR.
There are a few admin actions you would need to take, such as adding the GH workflow as a trusted publisher on the pypi package (you can specify the exact workflow if it is GHA, though maybe this is already what you are doing with circle CI).

[solegalli]

Could we make a GHA just to trigger the release on github? without affecting our current workflow on circleci?

[fkiraly]

Could we make a GHA just to trigger the release on github?

For that, you do not need a GHA - the GHA is only to trigger something from the release on GitHub.

You can simply make a release on GitHub through the "releases" menu
https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository#creating-a-release
This adds a release tag to the repository.

My opinion: doing this always for every release is a bit of a failure point if you do not use this to trigger pypi releases, since it increases the number of "independent actions" that you have to take.

[solegalli]

We should do it through circle ci.

Found this on a quick search: https://circleci.com/blog/publishing-to-github-releases-via-circleci/

@ChristopherGS would you be able to expand circleci workflow to release to github every time it releases to pypi?