ci/cd: build on push, release on tag

[xgui3783]

This PR adds CI/CD which:

• builds on each push
• publishes on pypi on tag

largely following guide from https://packaging.python.org/en/latest/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/#workflow-definition

---

edit: TODO: after merge, someone with pypi publish right (me, andrew etc) will need to continue the guide, specifically registering trusted publishing at https://pypi.org/manage/account/publishing/

[apdavison]

Looks good. Is there an easy way to check the tag string conforms to a valid version identifier?

This would allow tags to be used for other purposes, including tagging alpha, beta versions without creating PyPI releases for them.

[xgui3783]

Looks good. Is there an easy way to check the tag string conforms to a valid version identifier?

This would allow tags to be used for other purposes, including tagging alpha, beta versions without creating PyPI releases for them.

I think we can have a validation of the tag, and terminates early if fails.

I will polish this PR a bit, and ping you once ready.

[xgui3783]

ping @apdavison

can you take a look again? I have added a step which checks the tag matches ^[0-9]+\.[0-9]+\.[0-9]+$

which would allow:

• 6.1.0

(edited)

[apdavison]

hi @xgui3783 : I don't think we should publish dev, alpha, beta or rc versions to PyPI

[xgui3783]

good point. updated (up point is regex is also much simper)