Skip to content

revert: hash pinning on pypi publish workflow #980

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
bhearsum merged 1 commit into from
Jun 9, 2026
+2 −7
Merged

revert: hash pinning on pypi publish workflow #980

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
9 changes: 2 additions & 7 deletions .github/workflows/pypi-publish.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,14 +21,9 @@ jobs:
run: |
pip install build
python -m build
# NOTE: We deliberately pin this action to a commit SHA rather than the
# mutable `@release/v1` ref that PyPA recommends. The pin stops the
# action from being swapped out from under a workflow that holds PyPI
# publish (OIDC) rights; the cost is losing automatic upstream patches.
# Renovate offsets that by bumping the pinned SHA (tracked via the
# trailing `# vX.Y.Z` comment), so merge those bump PRs promptly.
- name: Publish package distributions to PyPI
uses: pypa/gh-action-pypi-publish@cef221092ed1bacb1cc03d23a2d87d1d172e277b # v1.14.0
# deliberately pinned to release/v1 to be allowed by our action pinning requirements
uses: pypa/gh-action-pypi-publish@release/v1
pypi-publish-pytest-taskgraph:
name: upload release to PyPI
if: startsWith(github.ref, 'refs/tags/pytest-taskgraph')
Expand Down