Skip to content

[gha] Bump open-edge-platform/orch-ci/.github/workflows/pre-merge.yml from 2026.0.17 to 2026.0.19 #1481

[gha] Bump open-edge-platform/orch-ci/.github/workflows/pre-merge.yml from 2026.0.17 to 2026.0.19

[gha] Bump open-edge-platform/orch-ci/.github/workflows/pre-merge.yml from 2026.0.17 to 2026.0.19 #1481

Status Success
Total duration 5m 59s
Artifacts 4

pre-merge.yml

on: pull_request
pre-checks
8s
pre-checks
pre-merge-pipeline  /  sanitize-project-folder
2s
pre-merge-pipeline / sanitize-project-folder
pre-merge-pipeline  /  license-compliance-check
14s
pre-merge-pipeline / license-compliance-check
pre-merge-pipeline  /  run-repo-pipelines
5m 23s
pre-merge-pipeline / run-repo-pipelines
pre-merge-pipeline  /  zizmor-scan
12s
pre-merge-pipeline / zizmor-scan
pre-merge-pipeline  /  secrets-gitleaks-scan
22s
pre-merge-pipeline / secrets-gitleaks-scan
pre-merge-pipeline  /  trivy-filesystem-scan
18s
pre-merge-pipeline / trivy-filesystem-scan
pre-merge-pipeline  /  trivy-critical-scan
22s
pre-merge-pipeline / trivy-critical-scan
pre-merge-pipeline  /  trivy-config-scan
22s
pre-merge-pipeline / trivy-config-scan
pre-merge-pipeline  /  bandit
21s
pre-merge-pipeline / bandit
Matrix: pre-merge-pipeline / Scan Docker Images for CIS
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
pre-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/
pre-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/
pre-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, tj-actions/changed-files@823fcebdb31bb35fdf2229d9f769b400309430d0. 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/
pre-merge-pipeline / trivy-critical-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/
pre-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, tj-actions/changed-files@ed68ef82c095e0d48ec87eccea555d944a631a4c. 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
gitleaks-results-pww6ve-edge-manage-docs Expired
175 Bytes
sha256:9f8f134d90efbaeca091925ba4bc5966058f26f3def8ada2bcbb8606fd7679d0
trivy-config-scan-edge-manage-docs
491 Bytes
sha256:43561db6c877ce8294585b036048f65cc0d34f8d844abf6719bc09fd58865525
trivy-fs-scan-report-edge-manage-docs
501 Bytes
sha256:ecda2ce46b7122bbf6f146c7bb698eb47d4c1efd0c09b9a5c23f42c482e7db38
zizmor-scan-report-edge-manage-docs
686 Bytes
sha256:d6dab08aa61e060a23c9dc8fca6f4459a2786210659d8c6607e5eb2b1113eac7