Skip to content

Pin the PyPI publish action by tag, not by commit SHA #175

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
isayev merged 1 commit into from
Aug 21, 2026
Merged

Pin the PyPI publish action by tag, not by commit SHA #175

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 14 additions & 1 deletion .github/workflows/publish.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,5 +45,18 @@ jobs:
name: python-package-distributions
path: dist/

# Pinned by TAG, not by commit SHA -- deliberately, and unlike every
# other action in this repository.
#
# This is a Docker-based action: it derives its own image reference from
# the ref it was invoked with, so `@<sha>` makes it pull
# ghcr.io/pypa/gh-action-pypi-publish:<sha>. Upstream publishes images
# tagged by VERSION only, so no such image exists and the pull fails with
# `manifest unknown` -- after a successful build, before PyPI is ever
# contacted. Verified against the registry: the v1.14.2 and v1.14.1 SHA
# tags both 404, while `v1.14.2` and `v1.14.1` both resolve.
#
# checkout/setup-python/upload-artifact above stay SHA-pinned: they are
# JavaScript actions, where the ref selects code rather than an image.
- name: Publish to PyPI
uses: pypa/gh-action-pypi-publish@a892a5a61159132606e93a2fa6f4358831b04d26 # v1.14.2
uses: pypa/gh-action-pypi-publish@v1.14.2
Loading