fix(build): pin hatchling <1.32 to fix twine check CI failure - #1095
Merged
Tranquility2 merged 1 commit intoAug 15, 2026
Merged
Conversation
hatchling>=1.32 emits Metadata-Version 2.5 in wheel/sdist metadata, which twine 6.2.0 (via packaging) does not yet recognize as valid, causing the 'Run twine check' CI step to fail with: InvalidDistribution: Invalid distribution metadata: '2.5' is not a valid metadata version. Pin hatchling to <1.32 so it keeps emitting Metadata-Version 2.4, which is compatible with the current twine/packaging toolchain. See pypa/twine#1327 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 6536a34d-6afa-4f02-81ed-89dc72586d04
alexanderankin
approved these changes
Aug 15, 2026
Tranquility2
deleted the
tranquility2/fix-hatchling-twine-metadata-version
branch
August 15, 2026 16:12
alexanderankin
pushed a commit
that referenced
this pull request
Aug 16, 2026
…1100) ## Problem The `Run twine check` CI step fails on all PRs (e.g. run [31887608422](https://github.com/testcontainers/testcontainers-python/actions/runs/31887608422/job/95019090461?pr=1090) on #1090) with: ``` Checking dist/testcontainers-4.15.0-py3-none-any.whl: ERROR InvalidDistribution: Invalid distribution metadata: '2.5' is not a valid metadata version ``` Root cause and original tracking issue: #1096. ## Fix `hatchling` emits `Metadata-Version: 2.5` in built wheel/sdist metadata. Rather than pinning `hatchling` back to an older version (as done in #1095), this upgrades `twine` to `>=7.0.0`, which officially added support for Metadata-Version 2.5, fixing the root cause instead of working around it. Supersedes #1095 as the preferred fix. ## Verification Ran locally: ``` uv build && uv run twine check dist/* ``` Wheel METADATA shows `Metadata-Version: 2.5` (hatchling unpinned), and both wheel and sdist pass `twine check` (`PASSED`).
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.
Fixes #1096
Problem
The
Run twine checkCI step fails on all PRs (e.g. run 31887608422 on #1090) with:Root cause
hatchling>=1.32started emittingMetadata-Version: 2.5in built wheel/sdist metadata. The pinnedtwine(6.2.0, viapackaging) doesn't yet recognize2.5as valid and rejects the distribution. This is unrelated to any specific PR's diff — it's an unpinned build-backend version issue. See pypa/twine#1327.Fix
Pin
hatchlingto>=1.26,<1.32inpyproject.toml's[build-system]so it keeps emittingMetadata-Version: 2.4, compatible with the current twine/packaging toolchain.Verification
Ran locally:
Wheel METADATA now shows
Metadata-Version: 2.4, and both wheel and sdist passtwine check(PASSED).