Release procedure for Wasserstein `v1.1.1`

[matthewfeickert]

now that this has gotten moved over to the thaler-lab GitHub org, could we work together to make a v1.1.1 release? (c.f. https://github.com/thaler-lab/Wasserstein/pull/5#issuecomment-1312059614).

Originally posted by @matthewfeickert in https://github.com/thaler-lab/Wasserstein/issues/5#issuecomment-1776499096

Following PR #5, this Issue can be used by @rikab and @matthewfeickert to try to coordinate the steps necessary to update the source code version information, make a GitHub Release, build all the wheels necessary, and then publish them to PyPI for a Wasserstien v1.1.1 release.

If @pkomiske has any release notes lying around those would be great. If not, this Issue can get turned into the start of some maintainer release docs.

[rkansal47]

Hi @matthewfeickert, have you looked into this further and is there some way I can help, particularly in releasing Python 3.11 wheels?

[matthewfeickert]

@rkansal47 No, I haven't yet, though thanks for the reminder that this is a todo.

First things I would recommend doing:

• [x] Having @pkomiske give @rikab maintainer permissions on PyPI for all the packages that the Thaler Lab should have maintainer control of (currently https://pypi.org/project/Wasserstein/ is just @pkomiske).
  • Done as of 2024-03-04
• [ ] Add MFA support for @rikab on PyPI (and I think @pkomiske too as that's now required for all package maintainers).
• [x] Split the CI components from the wheel building in CI
  • c.f. https://github.com/thaler-lab/Wasserstein/pull/8
• [x] Have the wheel building workflows run and upload the wheels to GitHub Actions as an artifact
• [ ] Have a seperate publishing workflow that downloads the artifacts and then publishes them using PyPI's Trusted Publishers.
• [ ] Release EnergyFlow v1.3.3 as the alpha is required for the Wasserstein tests to pass.

[matthewfeickert]

cc @rikab for the above (I forgot to add you earlier).

[j-s-ashley]

• [ ] Have the wheel building workflows run and upload the wheels to GitHub Actions as an artifact

Completed with #26 (and #43) 👍🏻

[matthewfeickert]

• [ ] Have a seperate publishing workflow that downloads the artifacts and then publishes them using PyPI's Trusted Publishers.

(Double posting across here and email — sorry in advance :grimacing:)

@rikab Thanks to great work by @j-s-ashley we're imminently close to being ready to publish new patch release wheels for EnergyFlow and Wasserstein to PyPI with fixes and new platform support added. Part of this includes transitioning publishing to use the more secure Trusted Publishers workflow.

This requires that either you link the PyPI projects to the GitHub repositories, or that you add @j-s-ashley to the PyPI projects with owner permissions (at least temporarily) for them to do it. Can you help us with this, ideally this week if possible?