Skip to content

fix: stage release downloads outside target folder so failures don't … #237

fix: stage release downloads outside target folder so failures don't …

fix: stage release downloads outside target folder so failures don't … #237

Triggered via push April 30, 2026 13:15
Status Failure
Total duration 3m 46s
Artifacts

scorecard.yml

on: push
Scorecard analysis
3m 38s
Scorecard analysis
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 warning
Scorecard analysis
Create Artifact Container failed: The artifact name SARIF file is not valid. Request URL https://pipelinesghubeus7.actions.githubusercontent.com/mYrNLLVCzQYQK4bAaPbjePMLqQKmzh5BN7jcujzhnvFhiHKtDz/_apis/pipelines/workflows/25167505483/artifacts?api-version=6.0-preview
Scorecard analysis
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11, actions/upload-artifact@97a0fba1372883ab732affbe8f94b823f91727db. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/