martinfleis
commented
8 months ago If it won't work, then we can always delete the tag, fix the action and try again.
Closed brendan-ward closed 5 months ago
martinfleis
commented
8 months ago If it won't work, then we can always delete the tag, fix the action and try again.
brendan-ward
commented
8 months ago Running into issues with TestPyPI in trying to get setup to test uploading packages there instead in order to test this PR. Looks like we'll need to wait for that to get fixed first.
martinfleis
commented
7 months ago @brendan-ward can you check again?
brendan-ward
commented
5 months ago Head's up: going to create (possibly multiple) 0.7.3a* tags to test upload of release artifacts to test pypi repository and upload of release artifacts to new versions on Github. Will delete test tags / versions as part of working this out.
Apologies in advance for the noise from Github about this.
brendan-ward
commented
5 months ago These updates successfully uploaded to the test PyPI repository and created a version (name had issues but that might have been due to running in a PR or config; will watch on next release).
Once this is merged, we can create a throw-away tag on main (maybe v0.7.3a4) to verify this works properly on the public PyPI repository.
brendan-ward
commented
5 months ago Here's how it looks in the UI:
Note: it appears to show the tag message as the body by default until we set the body manually; this appears to be coming from Github automatically rather than from the release action.
Going to delete the release / tag because I don't want anyone to try to pull this.
Resolves #317
This updates the release creation / deployment actions to supported versions, and migrates to trusted publishing on PyPI.
I enabled trusted publishing on PyPI for this project.
Not quite sure how best we can test this other than creating alpha / beta releases via tags. We could potentially temporarily switch this to point to the test PyPI server, and delete any releases this creates from Github.