Currently, the publish workflow is independent of the test workflow and triggered by publishing of a release. It may be desirable to:
Make sure tests run on tag that becomes a release. This probably means making sure tags trigger the test.
Check package uploads to TestPyPI before going to PyPI.
One possible solution is to build the package for distribution at the end of the test run (on every commit) and save it as an artifact. If the commit being tested is a version tag, it should then also go to TestPyPI.
If possible, the publish script should then just grab the artifact from the test, rather than build it again.
Currently, the publish workflow is independent of the test workflow and triggered by publishing of a release. It may be desirable to:
One possible solution is to build the package for distribution at the end of the test run (on every commit) and save it as an artifact. If the commit being tested is a version tag, it should then also go to TestPyPI.
If possible, the publish script should then just grab the artifact from the test, rather than build it again.