Fix PyPI publishing for Core Metadata 2.5 - #58
Merged
Merged
Conversation
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.
Problem
The trusted publisher for
v0.5.1rejected the valid wheel before upload:The build job installed current Twine and accepted the Core Metadata 2.5 artifacts, while the publishing job was pinned to
pypa/gh-action-pypi-publishv1.14.0 with an older metadata parser. The last successfulv0.5.0wheel used Metadata 2.4, which is why the skew surfaced only now.Failed release run: https://github.com/ebarti/agent-runtime-kit/actions/runs/33272630840
Fix
The official v1.14.2 release specifically upgrades the action to Twine 7 so it can publish Core Metadata 2.5 artifacts:
https://github.com/pypa/gh-action-pypi-publish/releases/tag/v1.14.2
Verification
v0.5.1wheel and sdist passtwine==7.0.0 check --strictv1.14.2tag commitgit diff --checkAfter merge, the existing immutable
v0.5.1tag can be republished with the workflow's manual tag input; no retagging or artifact mutation is required.