Add an OIDC release workflow so plexus-mesh can be published - #15
Merged
Merged
Conversation
Publishes to PyPI with trusted publishing, so no token is stored in the repo or in GitHub secrets. Actions are pinned by commit SHA rather than by tag, because a moving tag is a supply-chain hole and this is a project about provenance. Four gates run before anything can be published: 1. The tag must equal the version declared in pyproject.toml. 2. Every artifact digest is printed to the run log, so the bytes that were published can be matched later against the bytes that were built. 3. Every declared console script is resolved to a real callable in a clean venv. This is deliberately stronger than a `--version` smoke. A package whose entry point names a function that does not exist installs cleanly and fails on first use, and that is not hypothetical: this exact check caught accountable-surface shipping with an undeclared coherence_membrane dependency. 4. The sdist must itself build a wheel, so a source install is not left broken by a missing file in MANIFEST. Publishing uses PEP 740 attestations, so the index records which workflow built the bytes and a third party can check that without trusting us. The publish job stays skipped until the repository variable PYPI_ENABLED is set to true, so tagging exercises the whole build and smoke path before the trusted publisher exists. Co-Authored-By: Claude Opus 5 <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.
Part of making the Flywheel lane roster actually installable. Six lanes were advertised in
harness/lanes_registry.pyas pip installs that a user cannot obtain: three because the PyPI name belongs to an unrelated project, three because nothing was ever published. This repository is one of them.Why the release workflow is shaped this way
Publishing uses OIDC trusted publishing, so no token is stored in the repository or in GitHub secrets. Actions are pinned by commit SHA rather than by tag, because a moving tag is a supply-chain hole and this is a project about provenance.
Four gates run before anything can be published:
pyproject.toml.MANIFESTentry.Gate 3 is deliberately stronger than a
--versionsmoke, and it is not hypothetical. A--versioncheck would have passed four of these seven packages while three had no--versionhandler at all, and it would have missedaccountable-surfaceshipping a wheel that installs cleanly and then raisesModuleNotFoundError: No module named 'coherence_membrane'on first import. Resolving entry points caught that.Publishing uses PEP 740 attestations, so the index records which workflow built the bytes and a third party can verify that without trusting us.
The
publishjob stays skipped until the repository variablePYPI_ENABLEDis set totrue, so tagging exercises the whole build and smoke path before the trusted publisher exists.Before this can publish
A trusted publisher must be registered on PyPI for this project, owner
HarperZ9, workflowrelease.yml, environmentpypi. For a name that does not exist yet, that is a pending publisher; the first successful run creates the project.🤖 Generated with Claude Code