Repository navigation
Fix PyPI publish for metadata 2.5 and allow retrying a release - #22
Merged
Merged
Conversation
- Bump pypa/gh-action-pypi-publish v1.14.0 -> v1.14.2. Its twine 6.1 rejected the Metadata-Version 2.5 that current hatchling writes, which failed the 2.0.0 publish. v1.14.2 ships twine 7. - Add workflow_dispatch so a failed release can be retried; manual runs skip the version-changed check and rely on the existing-release check. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Problem
The 2.0.0 release run failed at "Publish package" (nothing was uploaded, no GitHub release created):
Current hatchling writes
Metadata-Version: 2.5.pypa/gh-action-pypi-publishv1.14.0 bundles twine 6.1, which doesn't accept it.Change
pypa/gh-action-pypi-publishto v1.14.2 (twine 7.0.0), pinned to SHA (same as labd/ecs-deplojo).workflow_dispatchto the release workflow so a failed release can be retried. A re-run would use the old workflow, and a new commit doesn't touchCHANGELOG.md. Manual runs skip the version-changed check; the existing-release check still prevents publishing the same version twice.Checks
uv build→twine checkwith twine 7.0.0 passes for the 2.0.0 wheel and sdist.pinact run --check --verify-comment, zizmor (only the trusted-publishing note).After merge: run "Release" manually on
masterto publish 2.0.0.