Update publish action

[ryjones]

This needs the logic removed from build.yml (the actual publishing part, not the release creating part)

[jamshale]

I'm not able to look at the pypi config yet, but this looks good 👍

[andrewwhitehead]

The logic in build.yml publishes packages for multiple platforms. We also don't support poetry (yet) although there's a PR starting that work.

[swcurran]

@andrewwhitehead — could you explain what your comment above means — what are the ramifications of what you are saying. I think I’m reading it that we need to remove the multiple platforms and the poetry update needs to be completed?

[andrewwhitehead]

We need to keep publishing the multiple platform packages. I'm not certain whether this new publishing method requires poetry or it can still support the old packaging method.

[jamshale]

I don't think this publishing method requires poetry. It's just how it's configured in pypi and with github actions. In theory the pypi publishing can just be removed from the build.yml pipeline and it can publish after, leaving the other platforms unchanged.

I haven't had the chance to study this yet though, so I could be off.

[ryjones]

I don't think this publishing method requires poetry. It's just how it's configured in pypi and with github actions. In theory the pypi publishing can just be removed from the build.yml pipeline and it can publish after, leaving the other platforms unchanged.

I haven't had the chance to study this yet though, so I could be off.

That was my thought - the completion of the other job could trigger the pypi job

[jamshale]

I'm working on another PR for this...

[swcurran]

@jamshale did a separate PR that handled the changes needed, and @andrewwhitehead updated the PyPi settings, so we should be good to go -- without this. We'll see how the release goes...