ci: stop publishing to PyPI from CI - #11
Merged
Merged
Conversation
Remove the tag-triggered publish workflow. Releases are uploaded to PyPI by hand, so the workflow only ever failed (no trusted publisher is configured) and left a red check on each release commit. CI's build job still builds and checks the sdist and wheel on every push. Add a "Releasing (maintainers)" section to CONTRIBUTING.md with the manual steps. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
CHANGELOG Unreleased entry for removing publish.yml, and a "Releasing (maintainers)" section in CONTRIBUTING.md with the manual build and upload steps. (Belongs with the previous commit; the first git add failed on the already-staged workflow deletion.) 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.
Releases go to PyPI by hand from now on, so this removes the tag-triggered
publish.ymlworkflow.Why: no trusted publisher is configured on PyPI, so the workflow failed on every release tag (v0.3.0, and now v0.3.1: run 35573070177) and left a red ✗ on the release commit.
What changes
.github/workflows/publish.yml. Pushing av*tag no longer triggers anything.twine checkon every push and PR, so broken packaging is still caught.CONTRIBUTING.mdgains a Releasing (maintainers) section: release PR → tag → GitHub release →python -m build,twine check,twine uploadfrom the tag.CHANGELOG.md: Unreleased entry.🤖 Generated with Claude Code