ci: PyPI Trusted Publishing workflow + README/OSS visibility polish - #3
Merged
Merged
Conversation
… docs - add .github/workflows/release.yml: builds sdist/wheel and publishes to PyPI via OIDC trusted publishing (pypa/gh-action-pypi-publish) whenever a GitHub release is published, using a dedicated 'pypi' environment and no stored API token - PyPI trusted publisher configured on pypi.org for felmonon/ agent-reliability-harness, workflow release.yml, environment pypi - README: add PyPI version, Python versions, downloads, CI, and license badges - README + docs/quickstart.md: update install instructions now that the package is live on PyPI (pip install agent-reliability-harness), keep the editable-checkout install as the contributor path - GitHub repo About sidebar website updated to the PyPI project page
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.
Why
Publishing v0.2.1 required manually creating a PyPI API token and running
uv publishby hand. That doesn't scale and means a long-lived (orfrequently-rotated) credential has to be managed. PyPI's Trusted Publishing
(OIDC) lets GitHub Actions authenticate to PyPI per-run with a short-lived
token, no stored secret required.
This PR also adds standard OSS visibility polish now that the package is
live.
Changes
.github/workflows/release.yml: new workflow, triggered onrelease: published. Builds the sdist/wheel in one job, then publishes toPyPI in a second job scoped to the
pypiGitHub Actions environment withid-token: writepermission (OIDC) usingpypa/gh-action-pypi-publish.No PyPI token is stored anywhere in the repo or its secrets.
felmonon/agent-reliability-harness,workflow
release.yml, environmentpypi(done on pypi.org, not part ofthis diff).
license badges; updated the quickstart to
pip install agent-reliability-harnessnow that it's live, keeping the editable-checkoutpath for contributors.
(done on github.com, not part of this diff; previously linked to the
author's portfolio page, changed at the user's explicit choice).
Verification
Not in this PR
first one to flow through this automated path — the manual token used for
v0.2.1 has already been revoked from PyPI.