chore migrate gihub actions to Action Manager#76
Open
jd-hatzenbuhler wants to merge 1 commit intomasterfrom
Open
chore migrate gihub actions to Action Manager#76jd-hatzenbuhler wants to merge 1 commit intomasterfrom
jd-hatzenbuhler wants to merge 1 commit intomasterfrom
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
1 participant
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
Migrate all GitHub Actions workflow files across ContentSquare repositories to use the Actions Manager Fork-and-Approved-Tag security model.
All direct upstream action references (e.g.
actions/checkout@v4) have been replaced with their ContentSquare-managed fork equivalents (e.g.ContentSquare/actions-checkout@approved-v4) usingplatform_github/allowed-actions.yamlas the source of truth.Motivation and Context
The Actions Manager implements a Fork-and-Approved-Tag security model to prevent supply chain attacks. Using direct upstream action references bypasses this model and will be blocked by security controls in the future.
This change ensures all workflows use only ContentSquare-controlled forks with security-reviewed approved tags, providing:
Breaking Changes
No breaking changes. The ContentSquare fork actions are functionally identical to their upstream counterparts — only the reference syntax changes.
Actions not present in
allowed-actions.yaml(no approved fork available yet) were left unchanged.How Has This Been Tested?
See the following CI runs in this PR