COPP-8737: Pin third-party actions#263
Open
Lachlan Kidson (lachlankidson) wants to merge 2 commits intomainfrom
Open
COPP-8737: Pin third-party actions#263Lachlan Kidson (lachlankidson) wants to merge 2 commits intomainfrom
Lachlan Kidson (lachlankidson) wants to merge 2 commits intomainfrom
Conversation
There was a problem hiding this comment.
Pull request overview
This PR pins all third-party GitHub Actions to specific commit hashes as a security measure to prevent supply-chain attacks. Each action reference is updated to use a commit SHA followed by a version tag comment for traceability.
Changes:
- Replaced version tags with commit hashes for all third-party actions across GitHub workflows
- Added version tag comments (e.g.,
# v2.10.0) after each commit hash for reference
Reviewed changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
.github/workflows/test-build.yml |
Pinned Docker setup, metadata, login, and build-push actions to commit hashes |
.github/workflows/release.yml |
Pinned Docker-related actions to commit hashes for release workflow |
.github/workflows/release-drafter.yml |
Pinned release-drafter action to commit hash |
.github/workflows/helm.yml |
Pinned Helm setup, chart-testing, and kind-action to commit hashes |
.github/workflows/e2e.yaml |
Pinned kind-action to commit hash for E2E testing |
.github/workflows/code-quality.yml |
Pinned CodeQL and golangci-lint actions to commit hashes |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Dimitar H (dimitar-hristov)
previously approved these changes
Feb 4, 2026
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
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.
COPP-8737
This PR uses pinact to pin all third-party actions to a specific hash as part of our Zizmor rollout. This is a necessary security precaution for preventing supply-chain attacks. See zizmor/unpinned-uses for more details.
What do I need to do?
These PRs should "just work" - an action pinned by a commit ID is functionally equivalent to one pinned by a tag as long as the tag hasn't been fiddled with after the initial release.
How can I be sure of these changes?
You can check that the tags match the commit ID via the releases page of any given action.
In the future when we enable Zizmor on all repositories you will get warning annotations on PRs if the hash does not match the version comment, see zizmor/ref-version-mistmatch for more details.
If you'd like to opt-in to this behaviour early please see Getting started with zizmor on your repos.
How do I maintain these pins going forwards?
Automatically:
Manually:
How this change was made
A list of repositories was created by performing a code search against the current actions allowlist, pinact was then applied:
This PR was generated using turbolift.