Skip to content

Fix: Site search issue during provisioning (#631) #194

Fix: Site search issue during provisioning (#631)

Fix: Site search issue during provisioning (#631) #194

Triggered via push April 16, 2026 04:23
Status Failure
Total duration 6m 10s
Artifacts 8
post-merge-pipeline  /  sanitize-project-folder
3s
post-merge-pipeline / sanitize-project-folder
post-merge-pipeline  /  version-bump
6s
post-merge-pipeline / version-bump
post-merge-pipeline  /  run-repo-pipelines
4m 51s
post-merge-pipeline / run-repo-pipelines
post-merge-pipeline  /  trivy-filesystem-scan
26s
post-merge-pipeline / trivy-filesystem-scan
post-merge-pipeline  /  trivy-config-scan
27s
post-merge-pipeline / trivy-config-scan
post-merge-pipeline  /  secrets-gitleaks-scan
26s
post-merge-pipeline / secrets-gitleaks-scan
post-merge-pipeline  /  zizmor-scan
14s
post-merge-pipeline / zizmor-scan
post-merge-pipeline  /  bandit
50s
post-merge-pipeline / bandit
post-merge-pipeline  /  ...  /  notify
post-merge-pipeline / notify-teams / notify
Matrix: post-merge-pipeline / sign-binaries
Matrix: post-merge-pipeline / sign-images
Matrix: post-merge-pipeline / scan-images
Fit to window
Zoom out
Zoom in

Annotations

1 error and 5 warnings
post-merge-pipeline / secrets-gitleaks-scan
Unable to upload "security-results/gitleaks/gitleaks-results-dx045p.sarif" as it is not valid SARIF: - instance.runs[0].results[5].locations[0].physicalLocation.region.startLine must be greater than or equal to 1 - instance.runs[0].results[5].locations[0].physicalLocation.region.startColumn must be greater than or equal to 1 - instance.runs[0].results[5].locations[0].physicalLocation.region.endLine must be greater than or equal to 1
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. 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/
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. 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/
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. 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/
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. 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/
post-merge-pipeline / scan-images (080137407410.dkr.ecr.us-west-2.amazonaws.com/edge-orch/orch-ui/infra:4.0.6-dev)
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. 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/

Artifacts

Produced during runtime
Name Size Digest
bandit-results-6w2h93
527 Bytes
sha256:fb088a17a6775a1be321d272161551e836eb379cb945f51b0f1480c5e6a9709a
cosign-image-0f0b53
690 Bytes
sha256:7c73d3fc99331866fc5a78e675f84791a0e9ef86fcae750f814c92a3a9413706
docker-images-apps-infra
351 MB
sha256:5c28d09223faa309f148c4343f2b28c9a033a42c40c435a2c0da438d412370ec
gitleaks-results-dx045p-apps-infra
7.74 KB
sha256:303c31588571cdb447e98cad588fbeaa833da0bc23c60aa941c73d01d554fde7
trivy-config-scan-apps-infra
2.01 KB
sha256:662eae7c41969b6ccd070bab6bbabd7b97995ea599f544329cf559a76ee948e7
trivy-fs-scan-report-fs-apps-infra
513 Bytes
sha256:be3d071a529e6e6d72f2e9b6b6d21dc681cd89c8030e09f42966b1c821cc97f5
trivy-image-vuln-080137407410.dkr.ecr.us-west-2.amazonaws.com_edge-orch_orch-ui_infra_4.0.6-dev
11.6 KB
sha256:4f1d302a1193a2f70a89677ec121e74ab520d0f925e39680d23e0cddf2373433
trivy-scan-report-sbom-apps-infra
18.8 KB
sha256:5ce0ea0e62b82775b9b6cda03bf72f5d39c6dc079dafe0b030a406e0a0c8d9d3