Fix pypa/gh-action-pypi-publish version to use SHA pinning #2198
+1
−1
Conversation
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
The previous change incorrectly used @v1 which doesn't exist. Pin to release/v1.13 SHA for security best practices. Signed-off-by: Salman Muin Kayser Chishti <13schishti@gmail.com>
seratch
approved these changes
Dec 17, 2025
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.
Summary
Fix incorrect version reference for
pypa/gh-action-pypi-publish.Problem
A previous PR incorrectly changed the action reference from
release/v1(valid branch) tov1(non-existent tag). Thev1tag doesn't exist in the pypa/gh-action-pypi-publish repository.Solution
Updated to use SHA pinning for release/v1.13:
This follows GitHub's security best practices for third-party actions by pinning to an immutable SHA.
Files Changed
.github/workflows/publish.yml