Skip to content

schedule secure-upload-folder #1096

schedule secure-upload-folder

schedule secure-upload-folder #1096

Triggered via schedule March 27, 2026 04:52
Status Failure
Total duration 34s
Artifacts 2
secure-upload-folder
8s
secure-upload-folder
secure-download-folder
10s
secure-download-folder
if-succeed
0s
if-succeed
if-failed
6s
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:c6614abf48e9eb31d12e8f607c9723580582f5ae2ade72725477a07df2903bee
my-artifact-noroot Expired
400 Bytes
sha256:ac36314edc13e18df8e133326ceb9c4f61554af478012355d7a9ac0a2670427a