ci(release): PyPI Trusted Publishing workflow + /release skill#358
Open
gloryfromca wants to merge 1 commit into
Open
ci(release): PyPI Trusted Publishing workflow + /release skill#358gloryfromca wants to merge 1 commit into
gloryfromca wants to merge 1 commit into
Conversation
GitHub had no publish path — the package was previously released from the (now-archived) GitLab mirror. Bring publishing to the public repo: - .github/workflows/release.yml: on a vX.Y.Z tag, build + smoke-test (make package) and upload to PyPI via Trusted Publishing (OIDC, no stored token), gated behind the `release` environment for manual approval. A guard step refuses to publish when the tag != pyproject version. - .claude/skills/release: /release documents the cut (bump version → CHANGELOG → tag → approve → verify) and the one-time PyPI trusted-publisher + GitHub environment setup. Requires two owner-only one-time steps before the first release (documented in the workflow header and the skill): register the GitHub trusted publisher on PyPI, and create the `release` environment with required reviewers. 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.
Brings PyPI publishing to the public GitHub repo. The package was previously released from the now-archived GitLab mirror; GitHub had no publish path at all.
What this adds
.github/workflows/release.ymlvX.Y.Ztag: build + smoke-test (make package) → upload to PyPI via Trusted Publishing (OIDC, no stored token), gated behind thereleaseenvironment. A guard step refuses to publish if the tag ≠pyprojectversion..claude/skills/release/SKILL.md/release— documents the release cut (bump version → CHANGELOG → tag → approve → verify) + the one-time setup.CLAUDE.md/releasealongside the other skills.everos→ Settings → Publishing → add a GitHub trusted publisher: ownerEverMind-AI, repoEverOS, workflowrelease.yml, environmentrelease.releasewith required reviewers (so every publish needs manual approval).Until (1) is done the upload step will fail; until (2) is done there is no approval gate. No PyPI API token is stored anywhere — the workflow mints a short-lived OIDC token at publish time.
Not included (deliberate)
covMakefile target exists but isn't wired into CI. Left out here — enabling an 80% gate needs a check of current GitHub coverage first, so it belongs in its own PR.publishstage is retired (repo archived); this replaces it as the sole release origin.🤖 Generated with Claude Code