fix(ci): publish to PyPI with trusted publishing - #17
Merged
Merged
Conversation
rye publish needs an API token and cannot exchange the GitHub OIDC token. Build with rye and upload with pypa/gh-action-pypi-publish instead.
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
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.
The 1.8.0 publish failed with
error: an access token is required.rye publishcannot use trusted publishing, so this builds with rye and uploads withpypa/gh-action-pypi-publish, which exchanges the GitHub OIDC token..github/workflows/is scaffolding that stlc keeps from the branch, so the nextstlc builddoes not revert this edit.After merge, run Publish PyPI by hand on
v1.8.0(or merge the 1.9.0 release PR).