Migrate to Trusted Publishing#3449
Open
facutuesca wants to merge 1 commit into
Open
Conversation
Contributor
Author
|
CI tests are failing on |
facutuesca
force-pushed
the
ft/trusted-publishing
branch
from
a3658ba to
a00dd03
Compare
Ninja3047
force-pushed
the
ft/trusted-publishing
branch
from
a00dd03 to
fd1e8c5
Compare
Contributor
Author
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.
This PR adapts the PyPI publishing workflow to use Trusted Publishing. It's based on our template, but leaving the build invocation the same for now.
I've also created the corresponding trusted publisher on PyPI:
