ci: SHA-pin all actions (org SHA-lock policy) - #599
Closed
davidsu wants to merge 1 commit into
Closed
Conversation
Actions were re-enabled on the org with a policy requiring third-party actions to be SHA-locked; tag-pinned workflows now die at startup (startup_failure, 0s). Pin every uses: reference to a full commit SHA with the tag kept as a trailing comment, matching the form the already-passing workflows use for actions/checkout. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Contributor
Author
|
Superseded by #600, which merged the identical pins (same SHAs — both resolved from the same tags on the same day). Closing; branch kept for reference. |
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
Actions were re-enabled on the base44 org (~12:20 today) with a new policy: third-party actions must be SHA-locked. Tag-pinned workflows now fail at startup (
startup_failure, 0s — observed on PR #598's branch, where only the already-SHA-pinned cooldown check survived).This PR pins every
uses:reference across all 13 workflows to a full commit SHA, keeping the tag as a trailing comment — the same form the surviving workflows already use foractions/checkout@3d3c42e…. GitHub-ownedactions/*are pinned too: it matches the surviving example and cannot violate any narrower reading of the policy.11d5960a326750d5838078e36cf38b85af67726249933ea5288caeca8642d1e84afbd3f7d6820020ece7cb06caefa5fff74198d8649806c4678c61a1caa296126883cff596d87d8935842f9db880ef25/0057852bfaa89a56745cba8c7296529d2fc39830ea165f8d65b6e75b540449e92b4886f43607fa02d3f86a106a0bac45b974a628896c90dbdf5c8093d7906e4ad0b1822421a7e6a35d5ca353c962f410fee1f7d63c2ff003460e3d139729b119787bc3490c5077e51419868618aeaa5fe8019c62421857d622d081ff2d3a40755e97629de92e3bcbfa7cf2ed5ef2e550a465a721f4f45e4a7d3c340c873e1dcce798a054427efc710af080354f8450d3c154c58428959ce8df70de7be546dd1250a005dd32156697e7477775783ea5526144ba13e8db5eec57747ce8Every SHA resolved today via
gh api repos/{owner}/{repo}/commits/{tag}. No behavior changes — pins only. The local composite action (./.github/actions/wix-gateway-proxy) contains no nesteduses:and needs nothing.No overlap with #598 (it only adds new files). This PR's own CI run doubles as the policy verification: workflows should now START (whether they pass is a separate question — see
suss-tasks/exec_tests_broken_by_wix_embargo.mdfor the known exec-suite red).🤖 Generated with Claude Code