Upgrade pypi-publish action to fix TestPyPI/PyPI release#73
Merged
Conversation
The pinned pypa/gh-action-pypi-publish@v1.8.11 bundles an old twine that only understands Metadata-Version up to 2.2, so it rejected wheels built by modern setuptools (which emit 2.4) with "Metadata is missing required fields: Name, Version". Track release/v1 so the action stays current. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
xginn8
approved these changes
Jul 2, 2026
nsteins
approved these changes
Jul 2, 2026
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
3 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.
What
Upgrade the PyPI publish step from the pinned
pypa/gh-action-pypi-publish@v1.8.11to the maintained@release/v1tag.Why
The
v1.4.0rc1TestPyPI release failed withInvalidDistribution: Metadata is missing required fields: Name, Version(run). The build itself was fine, but modernsetuptools(viapython -m build) emitsMetadata-Version: 2.4, and the old action bundles atwinethat only supports up to2.2, so it could not parse the artifacts. Our owntwine checkstep passed because it uses an up-to-datetwinefrom pip.How
Point the publish step at
pypa/gh-action-pypi-publish@release/v1, which the pypa project keeps current and which supports newer metadata versions. No other release logic changes; version is still derived from the git tag by setuptools_scm.🤖 Generated with Claude Code