ci(publish-python): twine upload --verbose + tag guard#43
Merged
Conversation
The v3.2.0 release fails on the second wheel upload to PyPI with a generic 400 Bad Request. twine swallows the response body unless --verbose is set; this commit adds the flag so the next retry surfaces the actual reason from PyPI.
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
2 participants
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.
Why
The v3.2.0 release (`release.yml` run #26338778339) fails on the second wheel upload to PyPI with a generic `400 Bad Request`. twine swallows the response body unless `--verbose` is set, so we currently can't see the actual reason.
Changes
Plan
After this PR merges to main, dispatch `publish-python.yml` manually from main against the v3.2.0 wheels, capture the verbose output, then iterate on the actual root cause.