Skip to content

prettier fix

prettier fix #2051

Re-run triggered March 30, 2026 12:43
Status Success
Total duration 1m 10s
Artifacts 6
devguard-scanner  /  ...  /  build-image
7m 20s
devguard-scanner / call-build-image / build-image
devguard-scanner  /  ...  /  secret-scanning
41s
devguard-scanner / call-secret-scanning / secret-scanning
devguard-scanner  /  ...  /  static-application-security-testing
57s
devguard-scanner / call-sast / static-application-security-testing
devguard-scanner  /  ...  /  infrastructure-as-code
41s
devguard-scanner / call-iac / infrastructure-as-code
devguard-scanner  /  ...  /  sca
39s
devguard-scanner / call-software-compsition-analysis / sca
devguard-scanner  /  ...  /  container-scanning
1m 18s
devguard-scanner / call-container-scanning / container-scanning
devguard-scanner  /  ...  /  deploy
2m 7s
devguard-scanner / call-deploy / deploy
devguard-scanner  /  ...  /  sign
37s
devguard-scanner / call-sign / sign
devguard-scanner  /  ...  /  attest
1m 3s
devguard-scanner / call-attest / attest
Fit to window
Zoom out
Zoom in

Annotations

1 warning
devguard-scanner / call-attest / attest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4. 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/