Merged
Conversation
|
Visit the preview URL for this PR (updated for commit 1595d2d): https://harmonizer-web--pr64-pin-action-versions-pipv17rp.web.app (expires Mon, 13 Apr 2026 21:22:56 GMT) 🔥 via Firebase Hosting GitHub Action 🌎 Sign: 0b46b8946d697564b3f98633c5cd230a6ede1236 |
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.
Overview
All GitHub Actions workflow dependencies are pinned to exact commit SHAs instead of mutable version tags.
Problem Statement
Using mutable version tags (e.g.
@v4) in GitHub Actions is a supply chain risk — a tag can be moved to point at a different, potentially malicious commit at any time without notice. Pinning to immutable commit SHAs ensures the exact code that was audited continues to run.Solution Approach
actions/checkout@v4with the SHA for v6.0.2 across all workflowsactions/setup-node@v4with the SHA for v6.3.0 in the shared runner actionactions/cache@v4with the SHA for v5.0.4 in the shared runner actionFirebaseExtended/action-hosting-deploy@v0with the SHA for v0.10.0 in both Firebase hosting workflowsBreaking Changes
None.