Use trusted publishing for PyPI #54
Open
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
This patch changes the CD workflow to use trusted publishing to PyPI. The main changes are: - The CD workflow is always executed and always publishes to TestPyPI. - For releases, the workflow also publishes to PyPI. - Instead of using access tokens, we use a GitHub environment for the publication jobs. This environment is configured on TestPyPI/PyPI and release jobs running in that environment can publish releases.
robin-nitrokey
requested review from
daringer,
mmerklinger and
sosthene-nitrokey
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 patch changes the CD workflow to use trusted publishing to PyPI. The main changes are:
TestPyPI works, PyPI still needs to be configured and tested.