Skip to content

Update to release 2026.0.0 #1465

Update to release 2026.0.0

Update to release 2026.0.0 #1465

Triggered via pull request March 27, 2026 09:17
Status Success
Total duration 7m 59s
Artifacts 4

pre-merge.yml

on: pull_request
pre-checks
6s
pre-checks
pre-merge-pipeline  /  sanitize-project-folder
3s
pre-merge-pipeline / sanitize-project-folder
pre-merge-pipeline  /  license-compliance-check
15s
pre-merge-pipeline / license-compliance-check
pre-merge-pipeline  /  run-repo-pipelines
7m 21s
pre-merge-pipeline / run-repo-pipelines
pre-merge-pipeline  /  zizmor-scan
9s
pre-merge-pipeline / zizmor-scan
pre-merge-pipeline  /  secrets-gitleaks-scan
16s
pre-merge-pipeline / secrets-gitleaks-scan
pre-merge-pipeline  /  trivy-filesystem-scan
27s
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
23s
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. 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 / 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/
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-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/

Artifacts

Produced during runtime
Name Size Digest
gitleaks-results-kt1got-edge-manage-docs Expired
175 Bytes
sha256:5f5f501c24c7251883ee2ec8a4a9f4f0ecb94decfb3f43ae7e6884c57e0db05d
trivy-config-scan-edge-manage-docs
490 Bytes
sha256:cb041275a692edd009f854a10ad3047ed64eb7eb52b3775aad9707937d4cb73b
trivy-fs-scan-report-edge-manage-docs
500 Bytes
sha256:c2bae66387122519a89ea0bb95a31072e16b0696ccf73f13b025fd2c91042f72
zizmor-scan-report-edge-manage-docs
687 Bytes
sha256:8ed26ccbf19a77bd8904d2092f788a9654fffc3ee8bd96dcfe3d9c63e8669d1d