…add-missing-actions-to-update-matrix

Add missing Actions to update matrix (515d00bc192ae4460e2122572ebc24020c58ea95)

…ems/update-detsys-ts-status-page` (`856a75af22949b76e23f6e54a1b4d27d8816cea4`)

…2949b76e23f6e54a1b4d27d8816cea4

Update `detsys-ts`: Merge pull request #113 from DeterminateSystems/update-detsys-ts-status-page

…92ae4460e2122572ebc24020c58ea95

Update detsys-ts: Merge pull request #51 from DeterminateSystems/add-missing-actions-to-update-matrix

Add missing Actions to update matrix

…6318ae30192c4bf23a73dc879bdb632

Update `detsys-ts`:

A caller of this action can lock this action to a specific commit. However because the action itself does not lock its dependent actions to a specific commit this opens the end-user up to possible supply-chain attacks if the dependent actions rewrite their tags.

This PR changes all third party actions to be explicitly locked.

Dependabot will still work and update these hashes for you


I also suggest installing https://github.com/ossf/scorecard in this repo. It will report about these kind of issues.

Note that you should in turn have to audit all the third party deps of the actions that your action depends on. In general this is all a bit of a mess and GitHub's security model is very meh

e.g. see ossf/scorecard#2189