chore(ci): use OIDC trusted publishing for pypi.org - #2559
Merged
Conversation
nejch
force-pushed
the
feat/oidc-publishing
branch
from
May 1, 2023 20:01
27f8a1c to
5b549c5
Compare
nejch
commented
May 1, 2023
Member
Author
|
@max-wittig could you take a look? Related settings are in The script is mostly from https://docs.pypi.org/trusted-publishers/using-a-publisher/#the-manual-way with a small fix, rather than using the whole extra action, so we can keep the current release flow. |
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.
Closes #2554
Tested on test.pypi.org, I've removed the static PYPI_TOKEN already. We can also remove the deploy token member now IMO