chore: switch to SHA-based workflow pins #2422
Merged
Conversation
This file contains 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
HashiCorp is in the process of rolling out a new security policy that requires us to pin the SHA hashes of any (external) GitHub Actions that we want to use in our workflows. I was very happy to see that `github-actions-version-updater` already has support for this built-in, thankfully!
xiehan
requested review from
mutahhir and
DanielMSchmidt
and removed request for
a team
ansgarm
approved these changes
Dec 13, 2022
DanielMSchmidt
approved these changes
Dec 15, 2022
|
I'm going to lock this pull request because it has been closed for 30 days. This helps our maintainers find and focus on the active issues. If you've found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
HashiCorp is in the process of rolling out a new security policy that requires us to pin the SHA hashes of any (external) GitHub Actions that we want to use in our workflows. I was very happy to see that
github-actions-version-updateralready has support for this built-in, thankfully!Further reading (inside HashiCorp): https://docs.google.com/document/d/10TCefPVlhFuh5cKn75rMqNFKZyP8qUK-BWPaaSEO01Q/edit?usp=sharing