When I introduced github-ci matrix builds in the github ci workflow, I accidentally also activated the matrix build for how the package is published to pypi. This is a bug - obviously, we don't want a matrix of different python versions race against each other, each trying to upload the same package to pypi.
This pull request introduces two separate ci jobs. One for testing (this job uses a matrix of different python versions), one for publishing (without using a matrix).
When I introduced github-ci matrix builds in the github ci workflow, I accidentally also activated the matrix build for how the package is published to pypi. This is a bug - obviously, we don't want a matrix of different python versions race against each other, each trying to upload the same package to pypi.
This pull request introduces two separate ci jobs. One for testing (this job uses a matrix of different python versions), one for publishing (without using a matrix).