Occasionally due to version-numbering constraints, setuptools_scm will select a concatenated version number to publish to PyPi which has already been used by another parallel branch. This causes that step to fail in the CI workflow.
Since dev versions are rarely being used on PyPi, I propose that we only build and publish the python package when we manually choose to. This can be done using the workflow_dispatch trigger.
Occasionally due to version-numbering constraints,
setuptools_scm
will select a concatenated version number to publish to PyPi which has already been used by another parallel branch. This causes that step to fail in the CI workflow.Since dev versions are rarely being used on PyPi, I propose that we only build and publish the python package when we manually choose to. This can be done using the workflow_dispatch trigger.