Dev-3097 Pin Actions to Specific SHA#82
Merged
kasjankotyniarsp merged 1 commit intoApr 8, 2026
Merged
Conversation
p-zielinski
approved these changes
Apr 7, 2026
|
The current test workflow failure is unrelated to changes introduced in this PR. As this PR only updates GH Actions, I'm proceeding with the merge. |
kasjankotyniarsp
deleted the
ms/dev-3097-gh-actions-pin-actions-to-specific-sha
branch
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
3 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.
Supply Chain Attacks - Poisoned Actions: Using Marketplace actions without pinning them to a specific commit SHA (e.g., using uses: actions/checkout@v4 instead of a unique hash). If a popular action creator's account is compromised, an attacker can push a malicious version that steals secrets (as seen in the famous tj-actions/changed-files incident).