Use symbolic action references in release workflows - #18
Merged
Merged
Conversation
samuel-williams-shopify
force-pushed
the
use-symbolic-action-tags
branch
from
September 21, 2026 11:55
fd7ebbc to
40b729a
Compare
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.
Use symbolic action references in the generated and checked-in release workflows: checkout v7, setup-ruby v1, attest v4, and upload-artifact v7. Document the moving-tag tradeoff. The standard CI workflows are handled separately in #17.
RubyGems credentials uses upstream's documented
@mainreference because it has no moving major tag. At review time this resolves to the existing pinned commit, so there is no action downgrade.Checkout v7 rejects explicit fork PR merge SHAs even after merge. Opt in only for the publish checkout, after the inspection job verifies the merged PR, ancestry, and generated release content. A workflow test checks this restriction; unmerged PR validation remains read-only.
Validation: 6 setup tests / 38 assertions, RuboCop, generated-workflow YAML parsing, and exact agreement between templates and checked-in release files. No live release was run.
References: checkout v7, RubyGems action usage.