Repository navigation
ci: bump build-and-inspect-python-package to v3.0.1 (fix twine check on metadata 2.5) - #432
Merged
Merged
Conversation
hatchling now emits Metadata-Version 2.5, which twine 6.2.0 (bundled with baipp v2.18) rejects in 'twine check --strict'. baipp v3.0.x ships twine 7.0.0, which supports metadata 2.5. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MiQ7iUinBNk9vMp1sGqZv1
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.
Requested by Ronny · project thread
🤖 Written by Claude Opus 5.5 via Claude Code for the execnet maintainers; I prompted it, it did the work, I read it.
Before: the
packagejob fails on every PR against current main (e.g. #431, #405, and the ChannelFileWrite encoding PR) attwine check --strictwithInvalidDistribution: Invalid distribution metadata: '2.5' is not a valid metadata version. Current hatchling (1.32.x) writesMetadata-Version: 2.5, and baipp v2.18 bundles twine 6.2.0, which does not know that version. The deploy workflow uses the same action, so a release would fail the same way.After: the
packagejob passes again. Locally, a wheel and sdist built from main passtwine check --strictwith twine 7.0.0 and fail with twine 6.2.0.How: bump
hynek/build-and-inspect-python-packagefromv2.18tov3.0.1intest.ymlanddeploy.yml. v3.0.0 updates the bundled tools to twine 7, which supports metadata 2.5, and v3.0.1 runs the action's own tool install outside the project directory. The action inputs and thePackagesartifact name are unchanged. Since v3 the action no longer force-movesv3/v3.0tags, so the full version is pinned.🤖 Generated with Claude Code
https://claude.ai/code/session_01MiQ7iUinBNk9vMp1sGqZv1
Generated by Claude Code