ci: pin the publish action to a commit, not a tag object - #6837
Merged
Conversation
#6836 used the sha of the v1.14.2 annotated tag. The action pulls ghcr.io/pypa/gh-action-pypi-publish tagged by github.action_ref, and no image is published for a tag object, so the republish failed with `manifest unknown`. Use the commit v1.14.2 points to. Same tree, same twine 7.0.0.
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
u9g
approved these changes
Aug 13, 2026
Contributor
Author
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.
Problem
#6836 pinned the publish action to
a892a5a, which is the annotated tag object ofv1.14.2, not the commit it points to. The 1.6.10 republish then stopped:gh-action-pypi-publishis a composite action. It builds a Docker action at run time fromgithub.action_refand pullsghcr.io/pypa/gh-action-pypi-publish:<that ref>. The pin must therefore be a ref with a published image. A tag object is not one.The registry agrees:
Fix
Pin the commit that
v1.14.2points to. It is the same tree #6836 intended, withtwine==7.0.0andpackaging==26.2, which accept theMetadata-Version: 2.5wheels that hatchling 1.32.0 produces.To confirm a pin of this kind, ask the API for the commit. A tag object gives 422: