The triggering workflow name for update version was incorrectly set to auto-publish (the name of the yaml file). It should have been Upload Package to PyPI (the name field of the workflow).
No easy way to retrigger the upload package to pypi workflow -- in fact using skip-existing is specifically recommended against by action authors: https://github.com/pypa/gh-action-pypi-publish. So, we'll just have to check if this works properly on the next release.
Also, the triggered PR doesn't run the appropriate tests bc of a github actions bug with the secrets.GITHUB_TOKEN (see stack overflow) --> so that is fixed by using my PAT -- see #308
The triggering workflow name for update version was incorrectly set to
auto-publish(the name of the yaml file). It should have beenUpload Package to PyPI(the name field of the workflow).No easy way to retrigger the upload package to pypi workflow -- in fact using
skip-existingis specifically recommended against by action authors: https://github.com/pypa/gh-action-pypi-publish. So, we'll just have to check if this works properly on the next release.Also, the triggered PR doesn't run the appropriate tests bc of a github actions bug with the
secrets.GITHUB_TOKEN(see stack overflow) --> so that is fixed by using my PAT -- see #308