feat: publish to PyPI on a python-vX.Y.Z tag - #10
Merged
Merged
Conversation
Adds .github/workflows/publish-python.yaml, modeled directly on python-sdk's publish-python.yaml: PyPI Trusted Publishing (OIDC via id-token: write in a dedicated 'pypi' GitHub environment), no stored API token, pinned action SHAs, twine check before upload. Triggered on a python-vX.Y.Z tag, kept deliberately separate from the existing vX.Y.Z tag that release.yml already uses for GitHub Releases — a PyPI publish is now an explicit, separate decision per release, not automatic. Requires a one-time PyPI-side step: registering this repo/workflow/ environment as a trusted publisher for this project name at https://pypi.org/manage/account/publishing/ (project name is not yet registered on PyPI, so this uses PyPI's pending-publisher flow).
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.
Adds
.github/workflows/publish-python.yaml, modeled directly onpython-sdk'spublish-python.yaml: PyPI Trusted Publishing (OIDC viaid-token: writein a dedicatedpypiGitHub environment), no stored API token, pinned action SHAs,twine checkbefore upload.Triggered on a
python-vX.Y.Ztag, kept deliberately separate from the existingvX.Y.Ztag thatrelease.ymlalready uses for GitHub Releases — a PyPI publish is now an explicit, separate decision per release, not automatic.Requires a one-time PyPI-side step before this can actually publish: registering this repo/workflow/environment as a trusted publisher for this project name at https://pypi.org/manage/account/publishing/ (the project name isn't registered on PyPI yet, so this uses PyPI's pending-publisher flow, which supports registering trust before a project exists).
Also creates the
pypiGitHub environment on this repo (via API, separately from this PR) so the workflow has something to run against.