fix: Pin GitHub Actions to commit SHAs - #1144
Merged
Merged
Conversation
PrekshithD-Microsoft
had a problem deploying
to
production
August 14, 2026 11:44 — with
GitHub Actions
Failure
Prajwal-Microsoft
approved these changes
Aug 17, 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.
This pull request updates the GitHub Actions workflow files to pin all third-party action dependencies to specific commit SHAs, rather than relying on version tags. This enhances the security and reliability of the CI/CD pipelines by ensuring that workflows always use the exact same version of each action, preventing unexpected changes from upstream updates.
The most important changes are:
Security and Reliability Improvements:
actions/checkout,docker/build-push-action,azure/login, etc.) in workflow files are now pinned to specific commit SHAs instead of version tags, reducing the risk of supply chain attacks and unexpected behavior from upstream changes. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19] [20] [21] [22] [23] [24] [25] [26] [27] [28] [29] [30] [31]Workflow Consistency:
Tooling and Dependency Management:
These changes collectively harden the CI/CD pipeline against supply chain vulnerabilities and make it easier to track and audit the exact versions of all automation dependencies.## Purpose
Does this introduce a breaking change?
How to Test
What to Check
Verify that the following are valid
Other Information