Publish to PyPI via trusted publishing - #116
Open
isayev wants to merge 1 commit into
Open
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
1 participant
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.
Switches the release publish step from the long-lived
PYPI_TOKENsecret to PyPI Trusted Publishing (OIDC): the publish job getsid-token: writeanduv publish --trusted-publishing alwaysreplaces the token flag.Merge prerequisite: on PyPI, the
aimnetproject must first have a trusted publisher registered (GitHub, ownerisayevlab, repositoryaimnetcentral, workflowon-release-main.yml, no environment) — requires the project owner. A second project owner should be added at the same time.The
PYPI_TOKENsecret stays untouched as a manual fallback; delete it after the first successful OIDC publish.