Add GitHub Actions workflow to semi-automatically publish a package to PyPI #60
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
The workflow runs whenever a new release is created, which is a manual process. The workflow runs in the "release" environment, which will be configured to require an additional manual approval step from someone other than the person who creates the release.
stephenjolly
changed the title
chrisn
approved these changes
Jun 20, 2024
Technically this is redundant because the same checks are run every time changes are merged, but better safe than sorry.
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 PR adds a new GitHub Actions workflow that runs whenever a new release is created, which is a manual process.
The workflow runs in the "release" environment, which will be configured to require an additional manual approval step from someone other than the person who creates the release.
The workflow is based on the one published in this Medium post, and uses the Action recommended in the official Python packaging guide. The Action uses OpenID Connect to securely convey ephemeral project-level authentication credentials to PyPI, so no secrets are stored or conveyed.