ci: pin pypi-publish action to its commit sha, not the tag-object sha#6
Merged
Conversation
The publish step failed with `manifest unknown` pulling ghcr.io/pypa/gh-action-pypi-publish:ecb4c3df… . That sha is the annotated tag *object* for v1.12.2 (what `git ls-remote refs/tags/v1.12.2` returns), not the commit it points to. gh-action-pypi-publish is a Docker action and GitHub pulls the image tagged with the ref you pass; pypa publishes that image keyed by the commit sha (15c56dba…), so the tag-object sha has no image. Verified against ghcr.io: tag-object sha → 404, commit sha → 200. Repin to the commit sha 15c56dba…; keeps SHA-pinning intact and resolves to the published image. (The other actions use lightweight tags, so their pins were already commit shas.)
chuckulele
approved these changes
Jun 3, 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 publish step failed with
manifest unknownpulling ghcr.io/pypa/gh-action-pypi-publish:ecb4c3df… . That sha is the annotated tag object for v1.12.2 (whatgit ls-remote refs/tags/v1.12.2returns), not the commit it points to. gh-action-pypi-publish is a Docker action and GitHub pulls the image tagged with the ref you pass; pypa publishes that image keyed by the commit sha (15c56dba…), so the tag-object sha has no image. Verified against ghcr.io: tag-object sha → 404, commit sha → 200.Repin to the commit sha 15c56dba…; keeps SHA-pinning intact and resolves to the published image. (The other actions use lightweight tags, so their pins were already commit shas.)