Repository navigation
CI: publish wheels to PyPI on version tags (Trusted Publishing, no secrets) - #4
Merged
morousg merged 1 commit intoJun 11, 2026
Conversation
New publish-pypi job: on v* tags (after build + codegen compile checks pass) the sdist+wheel are uploaded to PyPI with pypa/gh-action-pypi-publish using OIDC Trusted Publishing — no API tokens or secrets stored in GitHub. One-time setup required on pypi.org (documented in the workflow): add a pending publisher for project 'fkl-python' pointing at this repository, workflow wheels.yml, environment 'pypi'. The 'fkl-python' name is currently unclaimed on PyPI (verified via the simple index). skip-existing=true makes tag re-runs idempotent; the GitHub Release job is unchanged and runs in parallel.
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
2 participants
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.
Summary
Adds a
publish-pypijob to the wheels workflow: onv*tags, after the build + codegen compile checks pass, the sdist and wheel are uploaded to PyPI so users can simply:How it works
pypa/gh-action-pypi-publish— no API tokens or long-lived secrets stored in GitHub. PyPI verifies the upload comes from this exact repo + workflow + environment.needs:as the GitHub Release job (which is unchanged and runs in parallel).skip-existing: truemakes tag re-runs idempotent.One-time setup needed (whoever owns the PyPI side)
The
fkl-pythonname is currently unclaimed on PyPI (verified against the simple index). Before the first tagged release, someone (suggest: Oscar or the org) needs to register the pending publisher on pypi.org:…and create the
pypienvironment in this repo's GitHub settings (Settings → Environments → New environment →pypi; optionally add required reviewers as a release gate).After that, publishing a release is just:
git tag v0.7.0 && git push origin v0.7.0.These steps are also documented inline in the workflow file.