REL/CI: Automate release workflow #84
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Title of PR
This adds an automatic upload to PyPI when a GitHub Release is made.
https://packaging.python.org/en/latest/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/
It does require the version to already be bumped prior to making the release. So I think the recommended workflow would be to do all the tagging/versioning, then push to GitHub, then make a GitHub Release from that tag/commit. I automate all of those steps as well to pull the version from the tag, but I Poetry doesn't work as well with that style so I'm not sure what the recommended approach is with Poetry so I opted for manual for now and someone else can look into automating the poetry version bump.