Drop the Test PyPI publish stage - #10
Merged
Merged
Conversation
Releases now go straight to PyPI once the test matrix passes. The Download Distributions step is inlined into publish-to-pypi: it was a YAML anchor defined inside publish-test-pypi and aliased from there, so removing that job would have left a dangling alias. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
Summary
Removes the
publish-test-pypijob frompublish_dist.yml. A published release now runs the test matrix and goes straight to PyPI.The release pipeline goes from
testing → publish-test-pypi → publish-to-pypi → publish_docstotesting → publish-to-pypi → publish_docs, cutting the ~60s Test PyPI smoke-test wait and its propagation delay off every release.One thing worth noting
Download Distributionsis now written out inline inpublish-to-pypi. It had been a YAML anchor (&download_dist) defined inside the job being deleted and aliased (*download_dist) frompublish-to-pypi, so deleting the job outright would have left a dangling alias and broken the workflow parse. The step's content is unchanged.Test plan
testing,publish-to-pypi,publish_docs.publish-to-pypisteps resolve toDownload Distributions,Publish to PyPI,Smoke Test on PyPI, with the artifactname/run-id/pathinputs identical to before.publish_docsstill gates onpublish-to-pypi.release-triggered only, so PR checks cannot exercise it — it runs for real on the next published release.Follow-up (needs repo settings, not a code change)
The
test-pypiGitHub environment is now unused. It's harmless to leave, but you may want to delete it in Settings → Environments, along with any trusted-publisher entry for this repo on test.pypi.org.🤖 Generated with Claude Code