Skip to content

Release Notes 2026.0 #1446

Release Notes 2026.0

Release Notes 2026.0 #1446

Triggered via pull request March 19, 2026 14:38
Status Success
Total duration 10m 35s
Artifacts 4

pre-merge.yml

on: pull_request
pre-checks
8s
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
9m 45s
pre-merge-pipeline / run-repo-pipelines
pre-merge-pipeline  /  zizmor-scan
10s
pre-merge-pipeline / zizmor-scan
pre-merge-pipeline  /  secrets-gitleaks-scan
19s
pre-merge-pipeline / secrets-gitleaks-scan
pre-merge-pipeline  /  trivy-filesystem-scan
21s
pre-merge-pipeline / trivy-filesystem-scan
pre-merge-pipeline  /  trivy-critical-scan
19s
pre-merge-pipeline / trivy-critical-scan
pre-merge-pipeline  /  trivy-config-scan
14s
pre-merge-pipeline / trivy-config-scan
pre-merge-pipeline  /  bandit
19s
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-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 / 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 / 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/

Artifacts

Produced during runtime
Name Size Digest
gitleaks-results-g9yfr1-edge-manage-docs Expired
175 Bytes
sha256:25d4dc5a25f0135e3a020a3b020b68edc5ad89d8307d84a4da720cfbcc3abd61
trivy-config-scan-edge-manage-docs
490 Bytes
sha256:ef064e84ec3f56001554a80efa3a9b3a9e0facf016ee28df16d8341995b255ed
trivy-fs-scan-report-edge-manage-docs
500 Bytes
sha256:6cfe567cb8704a75adf464f3da3411550271b5215307b986119f828278b47d47
zizmor-scan-report-edge-manage-docs
687 Bytes
sha256:88988b54daa6072f10a4940cb114cb44166dcea2c0a8bfb04bc06f3003646244