fix(build): pin hatchling==1.27.0 so the wheel is twine-publishable - #3
Merged
Conversation
hatchling 1.28+ stamps Metadata-Version 2.5, which no released twine accepts yet — the v0.3.2 publish failed with InvalidDistribution. 1.27.0 emits 2.4 (twine PASSED locally, wheel + sdist). No code change. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014Bmmmgcida7VUntvBm16Xt
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 v0.3.2 release failed at the PyPI publish step: hatchling 1.28+ stamps wheels with
Metadata-Version: 2.5, which no released twine accepts yet (InvalidDistribution: '2.5' is not a valid metadata version). Nothing was published — it failed before upload.Pinning
hatchling==1.27.0makes the backend emitMetadata-Version: 2.4. Verified locally:twine checkPASSES on both wheel and sdist. No code change.After merge, the v0.3.2 tag is re-pointed to this commit and the release re-runs.
🤖 Generated with Claude Code