Merge pull request #395 from open-edge-platform/trustagent #133
hemanthsmpost-merge-helm.yml
on: push
post-merge-pipeline
/
sanitize-project-folder
2s
post-merge-pipeline
/
version-bump
0s
post-merge-pipeline
/
trivy-filesystem-scan
31s
post-merge-pipeline
/
trivy-config-scan
28s
post-merge-pipeline
/
secrets-gitleaks-scan
21s
post-merge-pipeline
/
zizmor-scan
19s
post-merge-pipeline
/
bandit
23s
post-merge-pipeline
/
...
/
notify
Matrix: post-merge-pipeline / sign-binaries
Matrix: post-merge-pipeline / sign-images
Matrix: post-merge-pipeline / scan-images
Annotations
5 warnings
|
post-merge-pipeline / secrets-gitleaks-scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, github/codeql-action/upload-sarif@1b549b9259bda1cb5ddde3b41741a82a2d15a841. 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/
|
|
post-merge-pipeline / bandit
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@a26af69be951a213d495a4c3e4e4022e16d87065, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, github/codeql-action/upload-sarif@1b549b9259bda1cb5ddde3b41741a82a2d15a841. 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/
|
|
post-merge-pipeline / trivy-config-scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. 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/
|
|
post-merge-pipeline / trivy-filesystem-scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. 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/
|
|
post-merge-pipeline / run-repo-pipelines
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/amazon-ecr-login@062b18b96a7aff071d4dc91bc00c4c1a7945b076. 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 | |
|---|---|---|---|
|
bandit-results-rqhq3a
Expired
|
583 Bytes |
sha256:364e58d42affcc64eb548f51daa237b7fe9d817c7b60899d80698ae39b75889d
|
|
|
gitleaks-results-fhi3qd-helm
Expired
|
7.05 KB |
sha256:94482e99a2201b5acdcd25370b7cc003b0ac24ed78d22815ffd8bc6108e6787d
|
|
|
trivy-config-scan-helm
|
13.5 KB |
sha256:a52ccec3bedff40ebc97f7d6431f1652b77716007d9445c187e3c0d763d79b5e
|
|
|
trivy-fs-scan-report-fs-helm
|
501 Bytes |
sha256:71895d44b40d491d17e238f9b73589af63c3854ee21ef9e38ffea9faae00d631
|
|
|
trivy-scan-report-sbom-helm
|
7.74 KB |
sha256:3d3408bd990f00dbc120bffe1cd9d1037ace6f5515dfbe040eeed580e6d2b860
|
|