Record the pinned deploy action version in its comment - #160
Merged
Conversation
The version comment beside the SHA-pinned plugin-deploy action read "stable" rather than naming the release. The pinned SHA resolves to tag 2.3.0, so the comment now records that, making the pin auditable at a glance. Only the comment changes; the commit SHA is untouched.
GaryJones
force-pushed
the
fix/action-version-comment
branch
from
June 17, 2026 16:19
d1ee7bd to
6f30c13
Compare
GaryJones
added
the
type: maintenance
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
1 participant
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
The release workflow pins
10up/action-wordpress-plugin-deployto a full commit SHA, which is what we want for supply-chain safety. The trailing comment, though, read# stablerather than naming a release, so the pin was not auditable at a glance: a reviewer could not tell which version that SHA represents without resolving it by hand, and "stable" misleadingly implies a moving target when the pin is in fact fixed.The pinned SHA (
54bd289b…) resolves to tag 2.3.0, so the comment now records that. Nothing functional changes: the commit SHA is untouched, so the workflow deploys using exactly the same action version as before, the label just now identifies it.