Skip to content

updated the SDK to use latest LMIv22 image for sdk v3.x #11

updated the SDK to use latest LMIv22 image for sdk v3.x

updated the SDK to use latest LMIv22 image for sdk v3.x #11

Triggered via pull request March 18, 2026 22:19
@access2rohitaccess2rohit
synchronize #5640
Status Failure
Total duration 2h 1m 0s
Artifacts

fortress-scan.yml

on: pull_request_target
collab-check
3s
collab-check
wait-for-approval
3s
wait-for-approval
fortress-scan
2h 0m
fortress-scan
Fit to window
Zoom out
Zoom in

Annotations

1 error and 2 warnings
fortress-scan
Build status: FAILED
collab-check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v7. 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/
fortress-scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/aws-codebuild-run-build@v1, aws-actions/configure-aws-credentials@v4. 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/