fix: pin hatchling below 1.32 so the wheel stays publishable - #33
Merged
Conversation
The v0.8.1 upload failed with: InvalidDistribution: Invalid distribution metadata: '2.5' is not a valid metadata version hatchling 1.32.0 started emitting Metadata-Version 2.5; the twine inside our pinned gh-action-pypi-publish (v1.14.0) only accepts up to 2.4, so it rejected the wheel before it ever reached the approval gate. Nothing in this repo changed to cause it — `requires = ["hatchling"]` was unpinned, so CI silently picked up a new backend. v0.8.0 published fine yesterday for that reason alone. Verified locally by building against each version: 1.30.1 -> 2.4, 1.31.0 -> 2.4, 1.32.0 -> 2.5. With the pin the wheel builds as 2.4 again. Pinning also restores build reproducibility, which an unpinned build backend cost us regardless of this failure. The forward-looking fix is to bump the publish action to a release whose twine accepts 2.5 (v1.14.2 is the candidate) and then widen this pin — that needs verifying against the real action, so it is deliberately not bundled here.
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.
fix(build): pin hatchling below 1.32 so the wheel stays publishable
The v0.8.1 upload failed with:
InvalidDistribution: Invalid distribution metadata: '2.5' is not a valid
metadata version
hatchling 1.32.0 started emitting Metadata-Version 2.5; the twine inside our
pinned gh-action-pypi-publish (v1.14.0) only accepts up to 2.4, so it rejected
the wheel before it ever reached the approval gate. Nothing in this repo
changed to cause it —
requires = ["hatchling"]was unpinned, so CI silentlypicked up a new backend. v0.8.0 published fine yesterday for that reason alone.
Verified locally by building against each version: 1.30.1 -> 2.4, 1.31.0 -> 2.4,
1.32.0 -> 2.5. With the pin the wheel builds as 2.4 again.
Pinning also restores build reproducibility, which an unpinned build backend
cost us regardless of this failure. The forward-looking fix is to bump the
publish action to a release whose twine accepts 2.5 (v1.14.2 is the candidate)
and then widen this pin — that needs verifying against the real action, so it
is deliberately not bundled here.