Repository navigation
ci: run twine upload with --verbose - #265
Merged
Merged
Conversation
Without it twine hides PyPI's response body, so a rejected upload only shows a bare "400 Bad Request" with no reason.
|
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.
The
v1.5.2backfill run failed uploading the new cp313 linux wheel with a bare400 Bad Request:https://github.com/manugarg/pacparser/actions/runs/37106338461/job/111155499329
twine only prints PyPI's response body (which carries the actual reason) when run with
--verbose, so add it to both upload steps. The token stays masked by Actions.Refs #263