SEC-090: Automated trusted workflow pinning (2023-07-31)

[hashicorp-tsccr]

This PR was auto-generated by hashicorp/security-tsccr/actions/runs/5713665194

You can alter the configuration of this automation via the hcl config in hashicorp/security-tsccr/automation

This is in support of RFC SEC-090 which is due to be implemented by EOQ2 FY24.

Please do the following:

• Approve and merge this PR if you are happy with the changes.
• Check if there are any untrusted third-party Actions in the workflow files and onboard them to the TSCCR.
• The yaml comments "# TSCCR: no entry for repository..." or "# TSCCR: no version of..." in the workflow files identifies an untrusted Action.
• If you have to onboard any third-party Actions, update and pin your workflows using the tsccr-helper tool after the Actions have been onboarded OR reach out to #team-prodsec and we can run this automation again.
• Verify that your Actions are still working as expected after pinning.

Please reach out to #team-prodsec if you have any questions.

[bflad]

TSCCR has been fixed and running the automation manually is now showing: All done: No workflow or action files were updated.

[github-actions]

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 contributions.
If you have 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.