Add PyPI release workflow #317
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I will YOLO-merge this on Wednesday June 5, unless approved earlier. Shortly after, I'll make another alpha release to make sure it all works as expected. |
24 tasks
|
If we'd ever be interested in conda releases, a package on conda-forge would be more of use.
|
Here's the code health analysis summary for commits Analysis Summary
|
|
Thanks for the review! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is another step to address #313.
The included workflow will make releases on PyPI and test releases on test.pypi.org.
I'm using an updated version of the trusted publisher workflow from: https://packaging.python.org/en/latest/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/
(This documentation has some outdated versions of the relevant GitHub actions, which was easy to fix.)
We will only properly see this in action (and validate that it works) after the pull request is merged into main, because that is the branch from which releases are made.