Add trusted publishing #209
Merged
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
2 participants
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.
We switched PyPI over to the
pymc-devsorg, and so now the old token shouldn't work. This is an excellent opportunity to switch to trusted publishing. I've already set up the link on PyPI.On the GitHub side, before merging this, all we need to do is go under Settings -> Environments and create a new environment called
pypiand configure required reviewers. (I don't personally have the necessary permissions, so you'll have to do it @aseyboldt)IMPORTANT: ensure that you click "Save protection rules" as pictured when configuring required reviewers, otherwise this will create a big security hole: