Fix the PyPI publish for Metadata-Version 2.5 - #8
Merged
Conversation
hatchling now emits Metadata-Version 2.5. The twine bundled in v1.14.0 rejects it with "InvalidDistribution: '2.5' is not a valid metadata version", which is what failed the v2.11.0 tag before any upload happened. v1.14.2 ships twine 7, which accepts 2.5. Pin resolved from the v1.14.2 tag object via the GitHub API, not copied. Signed-off-by: Tymofii Pidlisnyi <tima@aeoess.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.
The
v2.11.0tag run failed before any upload:hatchling now emits
Metadata-Version: 2.5and the twine bundled ingh-action-pypi-publishv1.14.0 does not accept it. The same pin published 2.10.0 in July, so this is upstream drift rather than a change on our side.v1.14.2 ships twine 7, which accepts metadata 2.5. The new pin
dc37677b2e1c63e2034f94d8a5b11f265b73ba33was resolved from thev1.14.2tag object through the GitHub API rather than copied from anywhere.Nothing reached PyPI, so 2.11.0 is still free. After this merges the tag moves to the new main head and the publish re-fires.