Skip to content

documentation link update for vbu apps #1448

documentation link update for vbu apps

documentation link update for vbu apps #1448

Triggered via pull request March 20, 2026 13:13
Status Success
Total duration 7m 20s
Artifacts 4

pre-merge.yml

on: pull_request
pre-checks
7s
pre-checks
pre-merge-pipeline  /  sanitize-project-folder
3s
pre-merge-pipeline / sanitize-project-folder
pre-merge-pipeline  /  license-compliance-check
11s
pre-merge-pipeline / license-compliance-check
pre-merge-pipeline  /  run-repo-pipelines
6m 35s
pre-merge-pipeline / run-repo-pipelines
pre-merge-pipeline  /  zizmor-scan
13s
pre-merge-pipeline / zizmor-scan
pre-merge-pipeline  /  secrets-gitleaks-scan
16s
pre-merge-pipeline / secrets-gitleaks-scan
pre-merge-pipeline  /  trivy-filesystem-scan
24s
pre-merge-pipeline / trivy-filesystem-scan
pre-merge-pipeline  /  trivy-critical-scan
25s
pre-merge-pipeline / trivy-critical-scan
pre-merge-pipeline  /  trivy-config-scan
24s
pre-merge-pipeline / trivy-config-scan
pre-merge-pipeline  /  bandit
23s
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 / 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. 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. 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-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/
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. 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. 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-s4t2ma-edge-manage-docs Expired
175 Bytes
sha256:5a31c81725f50415df69f7d0a8779dc90982d3728e15ec04f37dcdacbd89edee
trivy-config-scan-edge-manage-docs
490 Bytes
sha256:c835ddee6392c291bf34f323401a01510a34f056d3b1eff0160206264295047c
trivy-fs-scan-report-edge-manage-docs
500 Bytes
sha256:79e8034db1bc4d8baaf31a2c6ff127f5e15dc77bbff228adbf16c20f7715db4d
zizmor-scan-report-edge-manage-docs
687 Bytes
sha256:48f3fcd08010419dfaffafe1776aaeb734449eb16cc32d1e873dd13919e54f1d