feat(DTOSS-13028): Pin GitHub Actions to commit SHAs for enhanced security#311
Merged
Merged
Conversation
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
2 participants
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.
Description
This PR updates all GitHub Actions workflows to reference actions by immutable commit SHAs instead of version tags (e.g., @V3). This improves the security and integrity of our CI/CD pipelines by ensuring that workflows always run against a known, trusted version of each action.
What’s changed?
Context
GitHub Actions workflows in this repository were previously referencing actions using version tags (e.g., @V3). While convenient, these references are mutable and can change over time, introducing potential security and stability risks.
Recent security assessment guidance recommend pinning dependencies - including GitHub Actions - to specific commit SHAs. This ensures that workflows execute only verified and immutable code, reducing the risk of unintended changes or compromised upstream actions.
This update aligns our CI/CD pipelines with those best practices by making action dependencies explicit, auditable, and tamper-resistant.
Type of changes
Checklist
Sensitive Information Declaration
To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.