PyPI upload workflow uses trusted publisher instead of PyPI API token #26
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
rafa-be
force-pushed
the
pypi_thrusted_publisher
branch
from
dc488d2
to
793c5e7
Compare
Signed-off-by: rafa-be <[email protected]>
rafa-be
force-pushed
the
pypi_thrusted_publisher
branch
from
793c5e7
to
f01863b
Compare
JamieSlome
changed the title
JamieSlome
changed the title
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.
Uses trusted PyPI publisher credentials instead of PyPI API token when releasing the package.
@JamieSlome Please go to the "Publishing" tab from PyPI dashboard for Scaler and add Github as a trusted publisher, with the following values:
I couldn't test it, as I didn't have access to the PyPI package anymore.