Publish an sdist and stop partial releases on PyPI - #522
Merged
Conversation
youben11
approved these changes
Aug 3, 2026
philomath213
force-pushed
the
ci/publish-sdist-testpypi
branch
from
August 3, 2026 18:16
fa9ece0 to
d13675b
Compare
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
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.
Restructures the publish workflow into
build -> verify -> publish, and adds an opt-in TestPyPI rehearsal.twine uploaditself, so a failure partway through leaves a half-published release. The matrix now only uploads artifacts; a singlepublishjob does one upload.pip install tensealon any unlisted platform simply fails.MANIFEST.in. An sdist missingCMakeLists.txt,cmake/or the.protofiles still passestwine check, then fails for everyone building from source.release: published, keepingworkflow_dispatch.--extra-index-urlis required, as TestPyPI has no numpy.stamp_dev_version.shappends.dev<run_number>for rehearsals only — both indexes refuse to overwrite an existing version.Real releases are unaffected:
release: publishedalways targets PyPI with the existingPYPI_USERNAME/PYPI_PASSWORDsecrets.