[Security][AI] Fix GitHub Actions security vulnerabilities by pinning actions to commit SHAs #4
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 pull request was automatically generated by the
code-mend
service to address a security vulnerability detected in the codebase. While the identification of the issue is deterministic, this fix is not guaranteed to be correct and has not been fully tested. Please review the changes carefully to ensure they are correct, secure, and function as intended before merging.Fix Description
This pull request addresses GitHub Actions security vulnerabilities by pinning all third-party actions to specific commit SHAs to prevent supply chain attacks. The changes include:
hashicorp/packer-github-actions@master
tohashicorp/setup-packer@1aa358be5cf73883762b302a3a03abd66e75b232
(v3.1.0)canonical/has-signed-canonical-cla
to commit SHA1399a98cde76a66912c1a75b23f6f306ea814f1c
(v2)actions/checkout
to commit SHAf43a0e5ff2bd294095638e18286ca9a3d1956744
(v3)All actions are now pinned to verified commit SHAs, eliminating the security risks associated with mutable references like
@master
or@v2
tags.Next Steps
Generated by
code-mend
job a66ca988-4354-423f-a1b8-7b8e82436b17.For more information, see the associated ASR ticket.