Skip to content

Nightlies

Nightlies #1164

Triggered via schedule April 2, 2026 00:20
Status Failure
Total duration 3m 39s
Artifacts 7

nightlies.yml

on: schedule
call-container-scan  /  scan-backend-trivy
11s
call-container-scan / scan-backend-trivy
call-container-scan  /  scan-backend-snyk
17s
call-container-scan / scan-backend-snyk
call-container-scan  /  scan-frontend-trivy
1m 21s
call-container-scan / scan-frontend-trivy
call-container-scan  /  scan-frontend-snyk
55s
call-container-scan / scan-frontend-snyk
call-container-scan  /  scan-syft-requirements
1m 17s
call-container-scan / scan-syft-requirements
call-container-scan  /  scan-postgres-latest-trivy
42s
call-container-scan / scan-postgres-latest-trivy
call-container-scan  /  scan-postgres-latest-snyk
40s
call-container-scan / scan-postgres-latest-snyk
call-container-scan  /  scan-traefik-trivy
45s
call-container-scan / scan-traefik-trivy
call-container-scan  /  scan-traefik-snyk
27s
call-container-scan / scan-traefik-snyk
call-container-scan  /  scan-seaweedfs-trivy
39s
call-container-scan / scan-seaweedfs-trivy
call-container-scan  /  scan-seaweedfs-snyk
38s
call-container-scan / scan-seaweedfs-snyk
Matrix: call-conda-install / constall-install-syft
Matrix: call-pr-tests-linting / pr-tests-linting
Matrix: call-pr-tests-stack / pr-syft-image-test
Matrix: call-pr-tests-stack / pr-tests-integration-k8s
Matrix: call-pr-tests-stack / pr-tests-migrations-k8s
Matrix: call-pr-tests-stack / pr-tests-migrations
Matrix: call-pr-tests-stack / pr-tests-notebook-k8s
Matrix: call-pr-tests-stack / pr-tests-notebook-scenario-k8s-sync
Matrix: call-pr-tests-stack / pr-tests-scenarios-migrations
Matrix: call-pr-tests-stack / pr-tests-simulation-scenario-k8s
Matrix: call-pr-tests-stack / pr-tests-syft-integration
Matrix: call-pr-tests-syft / pr-tests-syft-notebook-python
Matrix: call-pr-tests-syft / pr-tests-syft-notebook-scenario-sync
Matrix: call-pr-tests-syft / pr-tests-syft-notebook-scenario
Matrix: call-pr-tests-syft / pr-tests-syft-notebook-single-container
Matrix: call-pr-tests-syft / pr-tests-syft-scenario-sync
Matrix: call-pr-tests-syft / pr-tests-syft-scenario
Matrix: call-pr-tests-syft / pr-tests-syft-security
Matrix: call-pr-tests-syft / pr-tests-syft-unit
Fit to window
Zoom out
Zoom in

Annotations

78 errors and 160 warnings
call-container-scan / scan-backend-trivy
Process completed with exit code 1.
call-container-scan / scan-backend-snyk
Process completed with exit code 1.
call-pr-tests-stack / pr-tests-migrations (ubuntu-latest, 3.12)
Process completed with exit code 1.
call-pr-tests-linting / pr-tests-linting (3.12)
Process completed with exit code 1.
call-pr-tests-stack / pr-tests-scenarios-migrations (ubuntu-latest, 3.12)
Process completed with exit code 1.
call-container-scan / scan-seaweedfs-snyk
Code Scanning could not process the submitted SARIF file: could not convert rules: invalid security severity value, is not a number: null
call-container-scan / scan-seaweedfs-snyk
Process completed with exit code 1.
call-pr-tests-syft / pr-tests-syft-unit (macos-latest, 3.12)
Process completed with exit code 4.
call-pr-tests-syft / pr-tests-syft-unit (windows-latest, 3.12)
The strategy configuration was canceled because "call-pr-tests-syft.pr-tests-syft-unit.macos-latest_3_12" failed
call-pr-tests-syft / pr-tests-syft-unit (windows-latest, 3.12)
The operation was canceled.
call-pr-tests-syft / pr-tests-syft-unit (windows-latest, 3.12)
Process completed with exit code 1.
call-pr-tests-syft / pr-tests-syft-security (ubuntu-latest, 3.12)
Process completed with exit code 1.
call-pr-tests-syft / pr-tests-syft-notebook-scenario (3.11, ubuntu-latest, python)
Process completed with exit code 1.
call-pr-tests-syft / pr-tests-syft-unit (3.11, ubuntu-latest)
The strategy configuration was canceled because "call-pr-tests-syft.pr-tests-syft-unit.macos-latest_3_12" failed
call-pr-tests-syft / pr-tests-syft-unit (3.11, ubuntu-latest)
The operation was canceled.
call-pr-tests-syft / pr-tests-syft-unit (3.10, ubuntu-latest)
The strategy configuration was canceled because "call-pr-tests-syft.pr-tests-syft-unit.macos-latest_3_12" failed
call-pr-tests-syft / pr-tests-syft-unit (3.10, ubuntu-latest)
The operation was canceled.
call-container-scan / scan-frontend-snyk
Process completed with exit code 1.
call-pr-tests-syft / pr-tests-syft-scenario (ubuntu-latest, 3.12, python, False)
Process completed with exit code 2.
call-pr-tests-syft / pr-tests-syft-unit (ubuntu-latest, 3.12)
The strategy configuration was canceled because "call-pr-tests-syft.pr-tests-syft-unit.macos-latest_3_12" failed
call-pr-tests-syft / pr-tests-syft-unit (ubuntu-latest, 3.12)
The operation was canceled.
call-pr-tests-syft / pr-tests-syft-notebook-scenario (3.10, ubuntu-latest, python)
The strategy configuration was canceled because "call-pr-tests-syft.pr-tests-syft-notebook-scenario._3_11_ubuntu-latest_pytho" failed
call-pr-tests-syft / pr-tests-syft-notebook-scenario (3.12, ubuntu-latest, python, True)
The strategy configuration was canceled because "call-pr-tests-syft.pr-tests-syft-notebook-scenario._3_11_ubuntu-latest_pytho" failed
call-pr-tests-syft / pr-tests-syft-scenario (3.10, ubuntu-latest, python)
The strategy configuration was canceled because "call-pr-tests-syft.pr-tests-syft-scenario.ubuntu-latest_3_12_python" failed
call-pr-tests-syft / pr-tests-syft-scenario (3.11, ubuntu-latest, python)
The strategy configuration was canceled because "call-pr-tests-syft.pr-tests-syft-scenario.ubuntu-latest_3_12_python" failed
call-pr-tests-syft / pr-tests-syft-scenario (3.12, ubuntu-latest, python, True)
The strategy configuration was canceled because "call-pr-tests-syft.pr-tests-syft-scenario.ubuntu-latest_3_12_python" failed
call-pr-tests-syft / pr-tests-syft-scenario-sync (3.10, ubuntu-latest, python)
The strategy configuration was canceled because "call-pr-tests-syft.pr-tests-syft-scenario-sync._3_12_ubuntu-latest_pytho" failed
call-pr-tests-syft / pr-tests-syft-scenario-sync (ubuntu-latest, 3.12, python, False)
The strategy configuration was canceled because "call-pr-tests-syft.pr-tests-syft-scenario-sync._3_12_ubuntu-latest_pytho" failed
call-pr-tests-syft / pr-tests-syft-notebook-scenario (ubuntu-latest, 3.12, python, False)
The strategy configuration was canceled because "call-pr-tests-syft.pr-tests-syft-notebook-scenario._3_11_ubuntu-latest_pytho" failed
call-pr-tests-syft / pr-tests-syft-scenario-sync (3.11, ubuntu-latest, python)
The strategy configuration was canceled because "call-pr-tests-syft.pr-tests-syft-scenario-sync._3_12_ubuntu-latest_pytho" failed
call-conda-install / constall-install-syft (ubuntu-latest, 3.12)
Process completed with exit code 1.
call-pr-tests-syft / pr-tests-syft-notebook-python (macos-latest, 3.12, python, tutorials, False)
Final attempt failed. Child_process exited with error code 2
call-pr-tests-syft / pr-tests-syft-notebook-python (3.11, ubuntu-latest, python, tutorials)
The strategy configuration was canceled because "call-pr-tests-syft.pr-tests-syft-notebook-python.macos-latest_3_12_python_" failed
call-pr-tests-syft / pr-tests-syft-notebook-python (3.12, ubuntu-latest, python, tutorials, True)
The strategy configuration was canceled because "call-pr-tests-syft.pr-tests-syft-notebook-python.macos-latest_3_12_python_" failed
call-pr-tests-syft / pr-tests-syft-notebook-python (3.10, ubuntu-latest, python, tutorials)
The strategy configuration was canceled because "call-pr-tests-syft.pr-tests-syft-notebook-python.macos-latest_3_12_python_" failed
call-pr-tests-syft / pr-tests-syft-notebook-python (ubuntu-latest, 3.12, python, tutorials, False)
The strategy configuration was canceled because "call-pr-tests-syft.pr-tests-syft-notebook-python.macos-latest_3_12_python_" failed
call-pr-tests-stack / pr-tests-notebook-k8s (ubuntu-latest, 3.12)
Process completed with exit code 1.
call-pr-tests-stack / pr-tests-notebook-k8s (ubuntu-latest, 3.12)
Process completed with exit code 1.
call-pr-tests-syft / pr-tests-syft-notebook-scenario-sync (3.11, ubuntu-latest, python)
Final attempt failed. Child_process exited with error code 1
call-pr-tests-syft / pr-tests-syft-notebook-scenario-sync (3.10, ubuntu-latest, python)
The strategy configuration was canceled because "call-pr-tests-syft.pr-tests-syft-notebook-scenario-sync._3_11_ubuntu-latest_pytho" failed
call-pr-tests-syft / pr-tests-syft-notebook-scenario-sync (3.12, ubuntu-latest, python, True)
The strategy configuration was canceled because "call-pr-tests-syft.pr-tests-syft-notebook-scenario-sync._3_11_ubuntu-latest_pytho" failed
call-pr-tests-syft / pr-tests-syft-notebook-scenario-sync (3.12, ubuntu-latest, python, True)
Final attempt failed. Child_process exited with error code 1
call-pr-tests-syft / pr-tests-syft-notebook-scenario-sync (ubuntu-latest, 3.12, python, False)
The strategy configuration was canceled because "call-pr-tests-syft.pr-tests-syft-notebook-scenario-sync._3_11_ubuntu-latest_pytho" failed
call-pr-tests-stack / pr-tests-notebook-scenario-k8s-sync (ubuntu-latest, 3.12)
Process completed with exit code 1.
call-pr-tests-stack / pr-tests-notebook-scenario-k8s-sync (ubuntu-latest, 3.12)
Process completed with exit code 1.
call-pr-tests-stack / pr-tests-simulation-scenario-k8s (ubuntu-latest, 3.12)
Process completed with exit code 1.
call-conda-install / constall-install-syft (macos-latest, 3.12)
Process completed with exit code 1.
call-conda-install / constall-install-syft (windows-latest, 3.12)
Process completed with exit code 1.
call-pr-tests-stack / pr-tests-migrations-k8s (ubuntu-latest, 3.12)
Process completed with exit code 1.
call-pr-tests-stack / pr-tests-migrations-k8s (ubuntu-latest, 3.12)
Process completed with exit code 1.
call-pr-tests-stack / pr-syft-image-test (ubuntu-latest, 3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5, dorny/paths-filter@v3. 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/
call-container-scan / scan-backend-trivy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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/
call-pr-tests-stack / pr-syft-image-test (ubuntu-latest, 3.12)
'before' field is missing in event payload - changes will be detected from last commit
call-container-scan / scan-backend-snyk
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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/
call-pr-tests-stack / pr-tests-migrations (ubuntu-latest, 3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-python@v5, dorny/paths-filter@v3. 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/
call-pr-tests-stack / pr-tests-migrations (ubuntu-latest, 3.12)
'before' field is missing in event payload - changes will be detected from last commit
call-pr-tests-linting / pr-tests-linting (3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-python@v5. 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/
call-pr-tests-linting / pr-tests-linting (3.12)
Failed to restore:
call-container-scan / scan-traefik-snyk
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: github/codeql-action/upload-sarif@v3. 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/
call-container-scan / scan-traefik-snyk
CodeQL Action v3 will be deprecated in December 2026. Please update all occurrences of the CodeQL Action in your workflow files to v4. For more information, see https://github.blog/changelog/2025-10-28-upcoming-deprecation-of-codeql-action-v3/
call-pr-tests-stack / pr-tests-scenarios-migrations (ubuntu-latest, 3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-python@v5, dorny/paths-filter@v3. 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/
call-pr-tests-stack / pr-tests-scenarios-migrations (ubuntu-latest, 3.12)
'before' field is missing in event payload - changes will be detected from last commit
call-container-scan / scan-seaweedfs-snyk
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, github/codeql-action/upload-sarif@v3. 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/
call-container-scan / scan-seaweedfs-snyk
CodeQL Action v3 will be deprecated in December 2026. Please update all occurrences of the CodeQL Action in your workflow files to v4. For more information, see https://github.blog/changelog/2025-10-28-upcoming-deprecation-of-codeql-action-v3/
call-container-scan / scan-seaweedfs-trivy
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/checkout@v4, github/codeql-action/upload-sarif@v3. 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/
call-container-scan / scan-seaweedfs-trivy
CodeQL Action v3 will be deprecated in December 2026. Please update all occurrences of the CodeQL Action in your workflow files to v4. For more information, see https://github.blog/changelog/2025-10-28-upcoming-deprecation-of-codeql-action-v3/
call-pr-tests-syft / pr-tests-syft-unit (macos-latest, 3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-python@v5, dorny/paths-filter@v3. 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/
call-pr-tests-syft / pr-tests-syft-unit (macos-latest, 3.12)
'before' field is missing in event payload - changes will be detected from last commit
call-container-scan / scan-postgres-latest-snyk
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, github/codeql-action/upload-sarif@v3. 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/
call-container-scan / scan-postgres-latest-snyk
CodeQL Action v3 will be deprecated in December 2026. Please update all occurrences of the CodeQL Action in your workflow files to v4. For more information, see https://github.blog/changelog/2025-10-28-upcoming-deprecation-of-codeql-action-v3/
call-pr-tests-syft / pr-tests-syft-notebook-single-container (ubuntu-latest, 3.11, remote, api/0.8)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-python@v5, dorny/paths-filter@v3. 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/
call-pr-tests-syft / pr-tests-syft-notebook-single-container (ubuntu-latest, 3.11, remote, api/0.8)
'before' field is missing in event payload - changes will be detected from last commit
call-container-scan / scan-postgres-latest-trivy
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/checkout@v4, actions/upload-artifact@v4, github/codeql-action/upload-sarif@v3. 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/
call-container-scan / scan-postgres-latest-trivy
CodeQL Action v3 will be deprecated in December 2026. Please update all occurrences of the CodeQL Action in your workflow files to v4. For more information, see https://github.blog/changelog/2025-10-28-upcoming-deprecation-of-codeql-action-v3/
call-container-scan / scan-traefik-trivy
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/checkout@v4, actions/upload-artifact@v4, github/codeql-action/upload-sarif@v3. 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/
call-container-scan / scan-traefik-trivy
CodeQL Action v3 will be deprecated in December 2026. Please update all occurrences of the CodeQL Action in your workflow files to v4. For more information, see https://github.blog/changelog/2025-10-28-upcoming-deprecation-of-codeql-action-v3/
call-pr-tests-syft / pr-tests-syft-unit (windows-latest, 3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5, dorny/paths-filter@v3. 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/
call-pr-tests-syft / pr-tests-syft-unit (windows-latest, 3.12)
'before' field is missing in event payload - changes will be detected from last commit
call-pr-tests-syft / pr-tests-syft-security (ubuntu-latest, 3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-python@v5, dorny/paths-filter@v3. 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/
call-pr-tests-syft / pr-tests-syft-security (ubuntu-latest, 3.12)
'before' field is missing in event payload - changes will be detected from last commit
call-pr-tests-syft / pr-tests-syft-notebook-single-container (ubuntu-latest, 3.12, remote, api/0.8)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-python@v5, dorny/paths-filter@v3. 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/
call-pr-tests-syft / pr-tests-syft-notebook-single-container (ubuntu-latest, 3.12, remote, api/0.8)
'before' field is missing in event payload - changes will be detected from last commit
call-pr-tests-syft / pr-tests-syft-notebook-scenario (3.11, ubuntu-latest, python)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-python@v5, dorny/paths-filter@v3. 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/
call-pr-tests-syft / pr-tests-syft-notebook-scenario (3.11, ubuntu-latest, python)
'before' field is missing in event payload - changes will be detected from last commit
call-pr-tests-syft / pr-tests-syft-unit (3.11, ubuntu-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-python@v5, dorny/paths-filter@v3. 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/
call-pr-tests-syft / pr-tests-syft-unit (3.11, ubuntu-latest)
'before' field is missing in event payload - changes will be detected from last commit
call-pr-tests-stack / pr-tests-syft-integration (ubuntu-latest, 3.12, local_server)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-python@v5, dorny/paths-filter@v3. 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/
call-pr-tests-stack / pr-tests-syft-integration (ubuntu-latest, 3.12, local_server)
'before' field is missing in event payload - changes will be detected from last commit
call-pr-tests-syft / pr-tests-syft-unit (3.10, ubuntu-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-python@v5, dorny/paths-filter@v3. 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/
call-pr-tests-syft / pr-tests-syft-unit (3.10, ubuntu-latest)
'before' field is missing in event payload - changes will be detected from last commit
call-container-scan / scan-frontend-snyk
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, github/codeql-action/upload-sarif@v3. 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/
call-container-scan / scan-frontend-snyk
CodeQL Action v3 will be deprecated in December 2026. Please update all occurrences of the CodeQL Action in your workflow files to v4. For more information, see https://github.blog/changelog/2025-10-28-upcoming-deprecation-of-codeql-action-v3/
call-pr-tests-syft / pr-tests-syft-scenario (ubuntu-latest, 3.12, python, False)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-python@v5, dorny/paths-filter@v3. 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/
call-pr-tests-syft / pr-tests-syft-scenario (ubuntu-latest, 3.12, python, False)
No files were found with the provided path: ./output-logs/. No artifacts will be uploaded.
call-pr-tests-syft / pr-tests-syft-scenario (ubuntu-latest, 3.12, python, False)
'before' field is missing in event payload - changes will be detected from last commit
call-pr-tests-syft / pr-tests-syft-unit (ubuntu-latest, 3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-python@v5, dorny/paths-filter@v3. 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/
call-pr-tests-syft / pr-tests-syft-unit (ubuntu-latest, 3.12)
'before' field is missing in event payload - changes will be detected from last commit
call-pr-tests-syft / pr-tests-syft-notebook-scenario (3.10, ubuntu-latest, python)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-python@v5, dorny/paths-filter@v3. 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/
call-pr-tests-syft / pr-tests-syft-notebook-scenario (3.10, ubuntu-latest, python)
'before' field is missing in event payload - changes will be detected from last commit
call-pr-tests-syft / pr-tests-syft-notebook-scenario (3.12, ubuntu-latest, python, True)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-python@v5, dorny/paths-filter@v3. 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/
call-pr-tests-syft / pr-tests-syft-notebook-scenario (3.12, ubuntu-latest, python, True)
'before' field is missing in event payload - changes will be detected from last commit
call-pr-tests-syft / pr-tests-syft-scenario-sync (3.12, ubuntu-latest, python, True)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-python@v5, dorny/paths-filter@v3. 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/
call-pr-tests-syft / pr-tests-syft-scenario-sync (3.12, ubuntu-latest, python, True)
No files were found with the provided path: ./output-logs/. No artifacts will be uploaded.
call-pr-tests-syft / pr-tests-syft-scenario-sync (3.12, ubuntu-latest, python, True)
'before' field is missing in event payload - changes will be detected from last commit
call-pr-tests-syft / pr-tests-syft-scenario (3.10, ubuntu-latest, python)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-python@v5, dorny/paths-filter@v3. 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/
call-pr-tests-syft / pr-tests-syft-scenario (3.10, ubuntu-latest, python)
'before' field is missing in event payload - changes will be detected from last commit
call-pr-tests-syft / pr-tests-syft-scenario (3.11, ubuntu-latest, python)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-python@v5, dorny/paths-filter@v3. 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/
call-pr-tests-syft / pr-tests-syft-scenario (3.11, ubuntu-latest, python)
'before' field is missing in event payload - changes will be detected from last commit
call-pr-tests-syft / pr-tests-syft-scenario (3.12, ubuntu-latest, python, True)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-python@v5, dorny/paths-filter@v3. 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/
call-pr-tests-syft / pr-tests-syft-scenario (3.12, ubuntu-latest, python, True)
'before' field is missing in event payload - changes will be detected from last commit
call-pr-tests-syft / pr-tests-syft-scenario-sync (3.10, ubuntu-latest, python)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-python@v5, dorny/paths-filter@v3. 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/
call-pr-tests-syft / pr-tests-syft-scenario-sync (3.10, ubuntu-latest, python)
'before' field is missing in event payload - changes will be detected from last commit
call-pr-tests-syft / pr-tests-syft-scenario-sync (ubuntu-latest, 3.12, python, False)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-python@v5, dorny/paths-filter@v3. 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/
call-pr-tests-syft / pr-tests-syft-scenario-sync (ubuntu-latest, 3.12, python, False)
'before' field is missing in event payload - changes will be detected from last commit
call-pr-tests-syft / pr-tests-syft-notebook-scenario (ubuntu-latest, 3.12, python, False)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-python@v5, dorny/paths-filter@v3. 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/
call-pr-tests-syft / pr-tests-syft-notebook-scenario (ubuntu-latest, 3.12, python, False)
'before' field is missing in event payload - changes will be detected from last commit
call-pr-tests-syft / pr-tests-syft-scenario-sync (3.11, ubuntu-latest, python)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-python@v5, dorny/paths-filter@v3. 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/
call-pr-tests-syft / pr-tests-syft-scenario-sync (3.11, ubuntu-latest, python)
'before' field is missing in event payload - changes will be detected from last commit
call-pr-tests-syft / pr-tests-syft-notebook-single-container (ubuntu-latest, 3.10, remote, api/0.8)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-python@v5, dorny/paths-filter@v3. 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/
call-pr-tests-syft / pr-tests-syft-notebook-single-container (ubuntu-latest, 3.10, remote, api/0.8)
'before' field is missing in event payload - changes will be detected from last commit
call-conda-install / constall-install-syft (ubuntu-latest, 3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, conda-incubator/setup-miniconda@v3. 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/
call-conda-install / constall-install-syft (ubuntu-latest, 3.12)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
call-container-scan / scan-syft-requirements
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5, actions/upload-artifact@v4, github/codeql-action/upload-sarif@v3. 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/
call-container-scan / scan-syft-requirements
CodeQL Action v3 will be deprecated in December 2026. Please update all occurrences of the CodeQL Action in your workflow files to v4. For more information, see https://github.blog/changelog/2025-10-28-upcoming-deprecation-of-codeql-action-v3/
call-container-scan / scan-frontend-trivy
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/checkout@v4, github/codeql-action/upload-sarif@v3. 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/
call-container-scan / scan-frontend-trivy
CodeQL Action v3 will be deprecated in December 2026. Please update all occurrences of the CodeQL Action in your workflow files to v4. For more information, see https://github.blog/changelog/2025-10-28-upcoming-deprecation-of-codeql-action-v3/
call-pr-tests-syft / pr-tests-syft-notebook-python (macos-latest, 3.12, python, tutorials, False)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-python@v5, dorny/paths-filter@v3, nick-fields/retry@v3. 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/
call-pr-tests-syft / pr-tests-syft-notebook-python (macos-latest, 3.12, python, tutorials, False)
Attempt 2 failed. Reason: Child_process exited with error code 2
call-pr-tests-syft / pr-tests-syft-notebook-python (macos-latest, 3.12, python, tutorials, False)
Attempt 1 failed. Reason: Child_process exited with error code 2
call-pr-tests-syft / pr-tests-syft-notebook-python (macos-latest, 3.12, python, tutorials, False)
'before' field is missing in event payload - changes will be detected from last commit
call-pr-tests-stack / pr-tests-integration-k8s (ubuntu-latest, 3.12, frontend network container_workload)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-python@v5, dorny/paths-filter@v3. 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/
call-pr-tests-stack / pr-tests-integration-k8s (ubuntu-latest, 3.12, frontend network container_workload)
'before' field is missing in event payload - changes will be detected from last commit
call-pr-tests-syft / pr-tests-syft-notebook-python (3.11, ubuntu-latest, python, tutorials)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-python@v5, dorny/paths-filter@v3, nick-fields/retry@v3. 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/
call-pr-tests-syft / pr-tests-syft-notebook-python (3.11, ubuntu-latest, python, tutorials)
Attempt 1 failed. Reason: Child_process exited with error code 2
call-pr-tests-syft / pr-tests-syft-notebook-python (3.11, ubuntu-latest, python, tutorials)
'before' field is missing in event payload - changes will be detected from last commit
call-pr-tests-syft / pr-tests-syft-notebook-python (3.12, ubuntu-latest, python, tutorials, True)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-python@v5, dorny/paths-filter@v3, nick-fields/retry@v3. 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/
call-pr-tests-syft / pr-tests-syft-notebook-python (3.10, ubuntu-latest, python, tutorials)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-python@v5, dorny/paths-filter@v3, nick-fields/retry@v3. 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/
call-pr-tests-syft / pr-tests-syft-notebook-python (3.12, ubuntu-latest, python, tutorials, True)
Attempt 1 failed. Reason: Child_process exited with error code 2
call-pr-tests-syft / pr-tests-syft-notebook-python (3.10, ubuntu-latest, python, tutorials)
Attempt 1 failed. Reason: Child_process exited with error code 2
call-pr-tests-syft / pr-tests-syft-notebook-python (3.12, ubuntu-latest, python, tutorials, True)
'before' field is missing in event payload - changes will be detected from last commit
call-pr-tests-syft / pr-tests-syft-notebook-python (3.10, ubuntu-latest, python, tutorials)
'before' field is missing in event payload - changes will be detected from last commit
call-pr-tests-syft / pr-tests-syft-notebook-python (ubuntu-latest, 3.12, python, tutorials, False)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-python@v5, dorny/paths-filter@v3, nick-fields/retry@v3. 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/
call-pr-tests-syft / pr-tests-syft-notebook-python (ubuntu-latest, 3.12, python, tutorials, False)
Attempt 1 failed. Reason: Child_process exited with error code 2
call-pr-tests-syft / pr-tests-syft-notebook-python (ubuntu-latest, 3.12, python, tutorials, False)
'before' field is missing in event payload - changes will be detected from last commit
call-pr-tests-stack / pr-tests-notebook-k8s (ubuntu-latest, 3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-python@v5, dorny/paths-filter@v3. 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/
call-pr-tests-stack / pr-tests-notebook-k8s (ubuntu-latest, 3.12)
'before' field is missing in event payload - changes will be detected from last commit
call-pr-tests-syft / pr-tests-syft-notebook-scenario-sync (3.11, ubuntu-latest, python)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-python@v5, dorny/paths-filter@v3, nick-fields/retry@v3. 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/
call-pr-tests-syft / pr-tests-syft-notebook-scenario-sync (3.11, ubuntu-latest, python)
Attempt 2 failed. Reason: Child_process exited with error code 1
call-pr-tests-syft / pr-tests-syft-notebook-scenario-sync (3.11, ubuntu-latest, python)
Attempt 1 failed. Reason: Child_process exited with error code 1
call-pr-tests-syft / pr-tests-syft-notebook-scenario-sync (3.11, ubuntu-latest, python)
'before' field is missing in event payload - changes will be detected from last commit
call-pr-tests-syft / pr-tests-syft-notebook-scenario-sync (3.10, ubuntu-latest, python)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-python@v5, dorny/paths-filter@v3, nick-fields/retry@v3. 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/
call-pr-tests-syft / pr-tests-syft-notebook-scenario-sync (3.10, ubuntu-latest, python)
Attempt 2 failed. Reason: Child_process exited with error code 1
call-pr-tests-syft / pr-tests-syft-notebook-scenario-sync (3.10, ubuntu-latest, python)
Attempt 1 failed. Reason: Child_process exited with error code 1
call-pr-tests-syft / pr-tests-syft-notebook-scenario-sync (3.10, ubuntu-latest, python)
'before' field is missing in event payload - changes will be detected from last commit
call-pr-tests-syft / pr-tests-syft-notebook-scenario-sync (3.12, ubuntu-latest, python, True)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-python@v5, dorny/paths-filter@v3, nick-fields/retry@v3. 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/
call-pr-tests-syft / pr-tests-syft-notebook-scenario-sync (3.12, ubuntu-latest, python, True)
Attempt 2 failed. Reason: Child_process exited with error code 1
call-pr-tests-syft / pr-tests-syft-notebook-scenario-sync (3.12, ubuntu-latest, python, True)
Attempt 1 failed. Reason: Child_process exited with error code 1
call-pr-tests-syft / pr-tests-syft-notebook-scenario-sync (3.12, ubuntu-latest, python, True)
'before' field is missing in event payload - changes will be detected from last commit
call-pr-tests-syft / pr-tests-syft-notebook-scenario-sync (ubuntu-latest, 3.12, python, False)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-python@v5, dorny/paths-filter@v3, nick-fields/retry@v3. 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/
call-pr-tests-syft / pr-tests-syft-notebook-scenario-sync (ubuntu-latest, 3.12, python, False)
Attempt 2 failed. Reason: Child_process exited with error code 1
call-pr-tests-syft / pr-tests-syft-notebook-scenario-sync (ubuntu-latest, 3.12, python, False)
Attempt 1 failed. Reason: Child_process exited with error code 1
call-pr-tests-syft / pr-tests-syft-notebook-scenario-sync (ubuntu-latest, 3.12, python, False)
'before' field is missing in event payload - changes will be detected from last commit
call-pr-tests-stack / pr-tests-notebook-scenario-k8s-sync (ubuntu-latest, 3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-python@v5, dorny/paths-filter@v3. 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/
call-pr-tests-stack / pr-tests-notebook-scenario-k8s-sync (ubuntu-latest, 3.12)
'before' field is missing in event payload - changes will be detected from last commit
call-pr-tests-stack / pr-tests-simulation-scenario-k8s (ubuntu-latest, 3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-python@v5, dorny/paths-filter@v3. 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/
call-pr-tests-stack / pr-tests-simulation-scenario-k8s (ubuntu-latest, 3.12)
No files were found with the provided path: ./output-logs/. No artifacts will be uploaded.
call-pr-tests-stack / pr-tests-simulation-scenario-k8s (ubuntu-latest, 3.12)
'before' field is missing in event payload - changes will be detected from last commit
call-conda-install / constall-install-syft (macos-latest, 3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, conda-incubator/setup-miniconda@v3. 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/
call-conda-install / constall-install-syft (macos-latest, 3.12)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
call-conda-install / constall-install-syft (windows-latest, 3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, conda-incubator/setup-miniconda@v3. 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/
call-conda-install / constall-install-syft (windows-latest, 3.12)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
call-pr-tests-stack / pr-tests-migrations-k8s (ubuntu-latest, 3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-python@v5, dorny/paths-filter@v3. 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/
call-pr-tests-stack / pr-tests-migrations-k8s (ubuntu-latest, 3.12)
'before' field is missing in event payload - changes will be detected from last commit

Artifacts

Produced during runtime
Name Size Digest
k8s-logs-integration-ubuntu-latest-1775089318
184 Bytes
sha256:6398bace32e4ae7032e0f0037553311071a3ef18f6c5909552f1bbc426bf7ed5
k8s-logs-notebook-ubuntu-latest-1775089323
184 Bytes
sha256:24945131fc2a53774ae00d8f45deef7d4a067d3c681003c4722146e6a09fa9b9
k8s-logs-notebook-ubuntu-latest-1775089345
180 Bytes
sha256:422679c920e8d328d334ebd54139aeacb46f825fd940c8cbdf40e7b0e03e32bb
k8s-logs-notebook-ubuntu-latest-1775089437
186 Bytes
sha256:cbc296252a9731904b51afb5f55b3343d198091eb5016102f7db717e1e0eacad
postgres-trivy-results.sbom.json
18.4 KB
sha256:eaf509e9e329cd4ed2970a2e221c16fcff0cb40887c211898737c8598d9fa015
syft.sbom.json
8.1 KB
sha256:d1855db5bc2da2b53dab1acbe7a2d842cd670a98742edc71b69b71af2a0f35d0
traefik-trivy-results.sbom.json
20.1 KB
sha256:f90d83f6f85bf2379a376bf124fe336c1153cc6941ec8987317101cb33d01034