ci: pin release-publish.yml actions to commit SHAs#1079
Merged
Conversation
Pin all GitHub Actions in the PyPI release workflow to full commit SHAs (with version comments) to mitigate moving-tag supply-chain risk. This workflow holds id-token: write and publishes to PyPI, so it is the highest-value target for pinning. Bumped to latest at time of pinning: - actions/checkout v7.0.0 - astral-sh/setup-uv v7 -> v8.2.0 - actions/upload-artifact v7 -> v7.0.1 - actions/download-artifact v8 -> v8.0.1 - pypa/gh-action-pypi-publish v1.14.0 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
Contributor
There was a problem hiding this comment.
Pull request overview
Pins GitHub Actions used by the PyPI release workflow to full commit SHAs to reduce moving-tag supply-chain risk in a workflow that publishes packages and holds id-token: write.
Changes:
- Replaced
uses: owner/action@vXreferences in the release workflow with full 40-char commit SHAs and version comments. - Updated the pinned versions for several actions in the release pipeline (checkout, setup-uv, upload/download artifact, PyPI publish).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Contributor
Author
|
Agree with copilot on removing |
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Collaborator
|
Thanks a lot, this is an important fix 🙏 |
noahho
approved these changes
Jun 29, 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
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.
Pin all GitHub Actions in the PyPI release workflow to full commit SHAs (with version comments) to mitigate moving-tag supply-chain risk. This workflow uses
id-token: writeand publishes to PyPI.https://docs.github.com/en/actions/reference/security/secure-use#using-third-party-actions
Bumped to latest at time of pinning:
Side note: Many of the actions have different sha-pinned versions.
Issue
No issue created, can make one if required.
Motivation and Context
Supply-chain attacks have exploited this attack vector, most of your other repo's abide by this, including workflows inside this repo.
Public API Changes
How Has This Been Tested?
It hasn't
Checklist
changelog/README.md), or "no changelog needed" label requested.