Automate the PyPI release workflow#158
Open
kmaziarz wants to merge 2 commits into
Open
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
1 participant
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.
So far, new versions of the
syntheseusPyPI package were published manually; ourRelease Stable Versionworkflow was only responsible for building docs and pushing a tag. This PR extends it to also build the package and publish it using OIDC trusted publishing. Moreover, it hardens the workflow from a security standpoint - it now verifies the tag is formatted correctly, the source branch is set tomain, and asks for approval from a second team member before doing the push. To make sure we don't push to PyPI if docs don't build, the workflow first verifies the docs without pushing, and then pushes out the package.