chore(ci): pin third-party GitHub Actions to commit SHAs - #137
Merged
Merged
Conversation
Replace floating third-party uses refs with the 2026-09-29 pin map and keep the tag comments. w3-lab-teardown-verify.yml is pin-only. The local vantio-prove action is unchanged.
The pin commit records third-party uses lines as owner/name@sha # tag. Workflow contract tests and the WS11 pin report still required floating tags, and the scanner dropped uses lines that carried a tag comment.
9 of 10 tasks
zacharybalicki
added a commit
that referenced
this pull request
Sep 29, 2026
Pin setup-node and upload-artifact inside the local vantio-prove composite to the #137 SHA map with # v4 comments. Regenerate the WS11 pin report so those two uses are digest_pinned.
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.
Pins floating third-party
uses:refs in.github/workflows/to the commit SHAs in ACTION-SHA-PINNING-PR-SPEC (2026-09-29). Inventory before the pin commit: tag-pinned dominant,any_sha_pinned_third_party: false.w3-lab-teardown-verify.ymlis pin-only (checkout, aws-actions, upload-artifact). This does not rewrite teardown or OIDC logic. AWS account IDs, role ARNs, regions, and environment names are unchanged. This does not publish and does not dispatch publish or teardown../.github/actions/vantio-provestays on floating@v4.Pin map:
actions/checkout@v4→11d5960a326750d5838078e36cf38b85af677262 # v4actions/setup-node@v4→49933ea5288caeca8642d1e84afbd3f7d6820020 # v4actions/setup-python@v5→a26af69be951a213d495a4c3e4e4022e16d87065 # v5pnpm/action-setup@v4→b906affcce14559ad1aafd4ab0e942779e9f58b1 # v4actions/upload-artifact@v4→ea165f8d65b6e75b540449e92b4886f43607fa02 # v4actions/attest-build-provenance@v2→e8998f949152b193b063cb0ec769d69d929409be # v2aws-actions/configure-aws-credentials@v6→e1253824e5c10ff9df46874f81ed3ec929e19cfd # v6pypa/gh-action-pypi-publish@release/v1→dc37677b2e1c63e2034f94d8a5b11f265b73ba33 # release/v1Each listed SHA resolved on GitHub and matches the peeled tag or the recorded
release/v1commit. No newer SHA was substituted.Follow-up on the same branch: release-governance contracts were still locking the floating tags, so a pin-only merge would turn the Release governance contract job red. This commit keeps the pin map and updates only those locks:
scripts/aws/test_w3_lab_teardown_workflow.pyandscripts/release/test_pypi_publish_workflow.pyexpect the SHA plus the tag comment. Role ARN, account id, region, environment, and permissions are unchanged.scripts/release/ws11/inventory.mjskeepsuses:lines written asowner/name@sha # tag, including a leading- uses:marker. Those rows aredigest_pinned: true. The local composite action stays unpinned.pin-report.json, the Optics dossier, andevaluations.jsonwere emitted from that scanner.00-INVENTORY.mdnow matches the report.