ci: pin GitHub Actions to full commit SHAs - #346
Merged
Merged
Conversation
The org now enforces a policy that every action referenced in a workflow must be pinned to a full 40-character commit SHA rather than a tag or branch. Every job in every workflow was failing within seconds at the "prepare workflow" step because none of our actions were pinned that way, which broke CI repo-wide for every PR. Resolve each tag/branch reference to the commit SHA it currently points at and keep the original version as a trailing comment, so the workflows stay both compliant and readable.
YuanYuYuan
added a commit
that referenced
this pull request
Sep 9, 2026
The org policy enforced on ZettaScaleLabs/hiroz rejects any workflow step whose action is not pinned to a full-length commit SHA. This job's five actions were still tag-pinned, so it would fail CI on that gate alone. Pin each to the SHA already used for the same action and version elsewhere in the repo (see #346), keeping the tag as a trailing comment.
YuanYuYuan
added a commit
that referenced
this pull request
Sep 9, 2026
The org policy enforced on ZettaScaleLabs/hiroz rejects any workflow step whose action is not pinned to a full-length commit SHA. This job's five actions were still tag-pinned, so it would fail CI on that gate alone. Pin each to the SHA already used for the same action and version elsewhere in the repo (see #346), keeping the tag as a trailing comment.
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 actions actions/checkout@v4, ... are not allowed in ZettaScaleLabs/hiroz because all actions must be pinned to a full-length commit SHA.This blocked CI repo-wide, for every PR, regardless of the PR's own content.Key Changes
uses: <owner>/<repo>@<tag-or-branch>reference across all nine workflow files (.github/workflows/*.yml) to the full commit SHA that ref currently points at.uses: actions/checkout@<sha> # v4), the standard convention so a human reading the workflow (and tools like Dependabot/Renovate) still know what version it is.uses:lines.What fails without this
Every CI run on every PR fails at the "prepare workflow" step within 2-4 seconds, before any real step executes, with the "not allowed ... must be pinned to a full-length commit SHA" error. This is not related to any PR's code changes.
Breaking Changes
None.