ci: bump gh-action-pypi-publish to v1.14.2 so metadata 2.5 wheels upload - #26
Merged
Merged
Conversation
The v0.4.0 publish failed before upload: the build step installs current
hatchling/build, which emit core packaging metadata 2.5, while the
pinned v1.14.0 publish action bundles a twine that rejects it
('2.5 is not a valid metadata version'). v1.14.2 carries twine v7,
which accepts 2.5 uploads. The workflow's own twine-check step already
passed — only the action's internal check was behind.
muralx
approved these changes
Aug 28, 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
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.
The v0.4.0 publish failed before upload: the build step installs current hatchling/build, which emit core packaging metadata 2.5, while the pinned v1.14.0 publish action bundles a twine that rejects it (
'2.5' is not a valid metadata version). v1.14.2 carries twine v7, which accepts 2.5 uploads. The workflow's own twine-check step already passed — only the action's internal check was behind.Recovery once merged: delete the unpublished v0.4.0 tag + GitHub Release (nothing reached PyPI) and re-run the release flow so the recreated tag carries the bumped action.