Security hardening (Github Actions workflows)

Update zgosalvez/github-actions-ensure-sha-pinned-actions action to v3 #156

Sign in to view logs

Triggered via pull request October 20, 2024 03:25

synchronize #36

renovate/zgosalvez-github-actions-ensure-sha-pinned-actions-3.x

Status Failure

Total duration 12s

Artifacts –

zzz_run.security.workflows.yaml

on: pull_request

ci_harden_security / Github Action security hardening

Annotations

5 errors and 1 warning

ci_harden_security / Github Action security hardening: .github/workflows/terraform.pull_requests.lint.yaml#L29

workflow command "set-output" was deprecated. use `echo "{name}={value}" >> $GITHUB_OUTPUT` instead: https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions

ci_harden_security / Github Action security hardening: .github/workflows/terraform.pull_requests.plan.yaml#L53

workflow command "set-output" was deprecated. use `echo "{name}={value}" >> $GITHUB_OUTPUT` instead: https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions

ci_harden_security / Github Action security hardening: .github/workflows/terraform.pull_requests.plan.yaml#L53

workflow command "set-output" was deprecated. use `echo "{name}={value}" >> $GITHUB_OUTPUT` instead: https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions

ci_harden_security / Github Action security hardening: .github/workflows/terraform.pull_requests.plan.yaml#L53

workflow command "set-output" was deprecated. use `echo "{name}={value}" >> $GITHUB_OUTPUT` instead: https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions

ci_harden_security / Github Action security hardening

Process completed with exit code 1.

ci_harden_security / Github Action security hardening

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@93ea575cb5d8a053eaa0ac8fa3b40d7e05a33cc8. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/