Repository navigation
🐛 fix(ci): bump build-and-inspect-python-package to v3.0.1 - #1147
Merged
Merged
Conversation
flit-core 4.0 writes Metadata-Version 2.5, which the twine 6.2.0 bundled in v2.18.0 rejects. v3.0.1 bundles twine 7.0.0, which accepts it.
henryiii
approved these changes
Aug 12, 2026
henryiii
left a comment
Contributor
There was a problem hiding this comment.
Yes. I wish there had been more of a delay in hatchling bumping to metadata 2.5 after twine updates.
Contributor
|
By the way, you can also just manually trigger Dependabot. |
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
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 "Build distribution" check fails on every PR since August 10, for example in run 31618820590, 31589143829, and 31574411778. flit-core 4.0 now writes
Metadata-Version: 2.5(PEP 794), and the twine 6.2.0 bundled in build-and-inspect-python-package v2.18.0 rejects it withInvalidDistribution: Invalid distribution metadata: '2.5' is not a valid metadata version. The bundled packaging 26.2 does know 2.5, but twine 6.2.0 overwritespackaging.metadata._VALID_METADATA_VERSIONSwith a hardcoded list that stops at 2.4, so the check fails regardless.Twine 7.0.0 dropped that override, and build-and-inspect-python-package v3.0.0 bundles it, with the changelog naming metadata 2.5 and PEP 794 support as the reason. This bumps the pin to v3.0.1, the latest release. Note that starting with v3 the action no longer force-pushes major version tags, so future bumps keep coming through the pinned commit hash as before.
Verified locally:
uv buildon this branch produces a wheel withMetadata-Version: 2.5,twine check --strictwith twine 6.2.0 plus packaging 26.2 (the v2.18.0 pins) reproduces the error, and twine 7.0.0 with the same packaging passes for both the sdist and the wheel.