Take the python dev-tool bumps with a coherent lockfile - #280
Merged
Conversation
Supersedes #274: dependabot widened the ranges (including the hatchling metadata workaround pin) without regenerating uv.lock, leaving the old twine to reject the new hatchling's Core Metadata 2.5. Twine 7 validates 2.5, so the pin can go — provided the lock actually upgrades with it.
nicklambourne
added a commit
that referenced
this pull request
Aug 17, 2026
Supersedes #274: dependabot widened the ranges (including the hatchling metadata workaround pin) without regenerating uv.lock, leaving the old twine to reject the new hatchling's Core Metadata 2.5. Twine 7 validates 2.5, so the pin can go — provided the lock actually upgrades with it.
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.
Scope
Supersedes #274. Dependabot widened the dev ranges — mypy <2.4, pytest-cov <8, twine <8, and hatchling <1.33 (straight through the metadata-workaround pin and its comment) — but did not regenerate
uv.lock, so the still-locked twine 6.2 rejects the Core Metadata 2.5 that hatchling ≥1.28 emits, failing the package check. Twine 7.0.0 validates Metadata 2.5, so the workaround pin can genuinely retire: this takes the same range bumps with the lockfile upgraded to match (twine 7.0.0, mypy 2.3.0).Validation
663 tests at 93.19% coverage, mypy 2.3.0 clean, ruff clean, and
uv build+ stricttwine checkpass with the locked toolchain.