Skip to content

schedule secure-upload-folder #1081

schedule secure-upload-folder

schedule secure-upload-folder #1081

Triggered via schedule March 12, 2026 04:39
Status Failure
Total duration 38s
Artifacts 2
secure-upload-folder
8s
secure-upload-folder
secure-download-folder
17s
secure-download-folder
if-succeed
0s
if-succeed
if-failed
5s
if-failed
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 3 warnings
secure-upload-folder
Process completed with exit code 1.
secure-upload-folder
Process completed with exit code 1.
secure-download-folder
Process completed with exit code 1.
secure-download-folder
Process completed with exit code 1.
secure-download-folder
Process completed with exit code 5.
secure-download-folder
Process completed with exit code 254.
if-failed
Process completed with exit code 123.
secure-upload-folder
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, slsa-framework/slsa-github-generator/.github/actions/compute-sha256@main. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
secure-download-folder
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093, slsa-framework/slsa-github-generator/.github/actions/compute-sha256@main. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
if-failed
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
my-artifact Expired
394 Bytes
sha256:5d4d3b157b0051d8497dfaa35a5f6d37279edf8e005b00653329ecee6bc37ce2
my-artifact-noroot Expired
399 Bytes
sha256:a39abc8577891d09e1b246e6c17ebac373e6511ac7f85bd3c2b389681725f7de