ci: migrate PyPI release to trusted publishing (OIDC)#2261
Open
bhimrazy wants to merge 3 commits into
Open
Conversation
bhimrazy
requested review from
andyland,
k223kim,
lianakoleva and
t-vi
as code owners
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.
What does this PR do?
Migrates the PyPI release workflow from token-based authentication to OIDC trusted publishing, following the same pattern as Lightning-AI/litData#827.
build,upload-release-assets, andpublish-pypijobsdist/through a GitHub artifact between jobsreleaseeventspermissions: id-token: write) and removes thePYPI_API_TOKENsecret requirementPre-requisite before merging: configure a trusted publisher on the litgpt PyPI project (Manage → Publishing) with owner
Lightning-AI, repolitgpt, workflowpublish-pkg.yml.PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in GitHub issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃