ci(release): publish orro to PyPI via Trusted Publishing on version tags#54
Merged
Conversation
Mirror the witnessd release pipeline: add a publish-pypi job using PyPA Trusted Publishing (OIDC, no stored token; PEP 740 attestations by default), gated to real version-tag pushes. This makes the ORRO repo the CI-published source of the orro package (superseding the ad-hoc 0.0.x uploads), so a tagged release publishes orro from here with provenance. Requires a PyPI trusted publisher on the existing 'orro' project: owner Moonweave-Systems, repository ORRO, workflow release.yml, environment pypi. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Mirrors the witnessd release pipeline: adds a
publish-pypijob (PyPA Trusted Publishing,pypa/gh-action-pypi-publish, OIDC no-token, PEP 740 attestations), gated to real version-tag pushes. Makes the ORRO repo the CI-published source oforro(0.1.0), superseding the ad-hoc 0.0.x token uploads.One-time PyPI setup before the next tagged release (existing
orroproject, no token): pypi.org → Manageorro→ Publishing → add a trusted publisher: ownerMoonweave-Systems, repoORRO, workflowrelease.yml, environmentpypi.🤖 Generated with Claude Code