Switch to PyPI Trusted Publishing, remove twine #614
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
| id-token: write | ||
| environment: | ||
| name: pypi | ||
| url: https://pypi.org/p/<your-pypi-project-name> |
There was a problem hiding this comment.
This URL needs to be fixed before this PR is merged.
I assume that <your-pypi-project-name> is micro-sam? Can someone confirm?
|
I'm marking this PR as a draft, until:
|
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.
Closes #613
This PR switches to PyPI deployment with Trusted Publishing (see the announcement and how trusted publishing works). It removes twine, and also removes the need for PyPI API tokens being used as github secrets.
This PR is not sufficient on its own, we (well, probably Constantin) also need to: