Setup PyPI publish on GH release using trusted publishing#1
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 provides a release process to publish when using the GitHub Release GUI. The Release GUI can auto-generate release notes from commit messages since the last release (I love this feature 😁 but the generated release notes always need massaging unless you're really consistent about using PRs and carefully titling the PRs as if they are part of a changelog), and it will also create a tag at the same time.
The mechanism to push to PyPI is "trusted publishing", the most secure available mechanism. GitHub sends information about the action and repository that wants to publish across a trusted channel, PyPI checks that that action and repository are in the approved list (you need to set this up in the PyPI GUI), and once that is verified, short-lived tokens are used behind-the-scenes to authenticate the publication.
https://docs.pypi.org/trusted-publishers/
Having these tags will make it much easier to debug the build failures we're seeing in conda-forge because we'll be able to use Git to compare dependencies between releases using those tags.