Update publishing workflow

LiamPattinson commented 6 months ago

In advance of our imminent next release (Issue https://github.com/pyro-kinetics/pyrokinetics/issues/316), I've updated the PyPI publishing workflow to meet the new standards. The previous method of storing PyPI usernames and passwords with GitHub secrets is now obsolete, and PyPI now prefers to use 'trusted publishers' -- this page explains how to configure everything. I think @bpatel2107 or @ZedThree will have to configure things on the PyPI side.

Things changed in this update:

Now builds a distribution on every push
Calls twine check to ensure the packages are being built correctly
Uploads built packages as an artefact which can be downloaded from the action
Introduces a second job which publishes on new releases
Publishing will not work anymore unless trusted publishers are set up

LiamPattinson commented 6 months ago

While I'm at it, just updated the upload/download-artifact actions as the old versions are due to be deprecated within the year.

bpatel2107 commented 6 months ago

I've followed the instructions and added in a trusted publisher (I think)

ZedThree commented 6 months ago

@bpatel2107 Should we get this in and then release 0.7.0?

bpatel2107 commented 6 months ago

There are quite a few smaller issues I am working on that I would like to get in. We can of course do another release as we have them quite far apart as is. Maybe in a week or two we can do 0.7.1?

ZedThree commented 6 months ago

More frequent, smaller releases is fine. It's only a few button clicks to make a new one :)

bpatel2107 commented 6 months ago

I just want #324 merged and then we can publish as that is quite important. As soon as that is merged (should be done now) I'll make a new release.

pyro-kinetics / pyrokinetics

Update publishing workflow #340