Use trusted publishing on PyPI #597
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
HGSilveri
force-pushed
the
hs/trusted-publishing
branch
from
b2463c7 to
0ffb05a
Compare
madagra
approved these changes
Oct 13, 2023
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.
publish.ymlworkflow to use a Trusted Publisher instead of a token (thus avoiding storing tokens as secrets)twinewith the official PyPI Publish Github ActionreleaseGithub environment to better manage the release processThe changes were tested through a dummy deployment to TestPyPI and then replicated for the PyPI case (without a dummy deployment so as to not pollute the official repo).