Release 0.3.1 of PyTNG

[IAlibay]

A release of pytng is necessary in order to allow for py3.12 support - this is blocking the core library here: MDAnalysis/mdanalysis#4327

[hmacdope]

Ill cut now?

[IAlibay]

@hmacdope what's your release procedure? It should match the new deployment workflow

[IAlibay]

New release procedure should be:

1. Make & push tags
2. Check GH action for testpypi push worked fine
3. Make release
4. Check GH action for pypi push worked fine

[hmacdope]

Normally, cut tag on main, pull, then push to PyPi from my own computer, I assume the new workflow makes it easier?

[IAlibay]

Normally, cut tag on main, pull, then push to PyPi from my own computer, I assume the new workflow makes it easier?

yeah you don't need to do any of that anymore, wheel building should be automatic - assuming the workflow doesn't have any bugs (it'll probably fail the first time around knowing how these things go).

[hmacdope]

Cutting directly on github will trigger or do i need to actually push the tags from local?

[IAlibay]

@hmacdope

Yes, just doing this will work:

git tag -m "release 0.3.1 of pytng" v0.3.1
git push --tags origin

Then when CI passes you can just do a release using that new tag.

[IAlibay]

Looks like the wheel upload went fine: https://test.pypi.org/project/pytng/#files

Should be good to cut a release.

[hmacdope]

Legendary, thanks so much. Good practice for me to understand the no-local workflow as well.

[hmacdope]

Done and tested.

[IAlibay]

@hmacdope you're probably going to need to update the conda-forge recipe quite a bit because of the numpy pins, iirc the current defaults aren't the same as what conda-forge expects.

[IAlibay]

I don't think I'm a maintainer for that recipe but if you ping me for review I can add the necessary changes.

[hmacdope]

Cheers, will do. Thanks for sorting this out I was very slow, my apologies.