Skip to content

test-e2e-semgrep-ci #399

test-e2e-semgrep-ci

test-e2e-semgrep-ci #399

Triggered via schedule November 2, 2024 20:43
Status Success
Total duration 5m 31s
Artifacts
Get Inputs
0s
Get Inputs
semgrep-ci-on-pr
8s
semgrep-ci-on-pr
semgrep-ci
5m 9s
semgrep-ci
semgrep-ci-fail-open
14s
semgrep-ci-fail-open
semgrep-ci-fail-open-blocking-findings
5m 11s
semgrep-ci-fail-open-blocking-findings
wait-for-checks
1m 9s
wait-for-checks
notify-failure
0s
notify-failure
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
semgrep-ci-on-pr
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
semgrep-ci-on-pr
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
semgrep-ci-fail-open
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
wait-for-checks
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
semgrep-ci
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
semgrep-ci-fail-open-blocking-findings
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/