Cap hatchling <1.27 so wheels publish to PyPI - #4
Merged
Merged
Conversation
shellygr
approved these changes
Aug 28, 2026
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.
hatchling >=1.27 stamps wheels with Metadata-Version 2.5 (PEP 639
license-expression / license-file fields). The twine bundled in the
pinned pypa/gh-action-pypi-publish image cannot validate 2.5, so the
v0.2.0 release built successfully but failed at the publish step with
"InvalidDistribution: '2.5' is not a valid metadata version" — nothing
reached PyPI.
Capping the build backend below 1.27 emits Metadata-Version 2.3, which
that action's twine and PyPI both accept. Verified locally: twine check
passes under packaging==24.0 (which reproduced the failure on 2.5).