1.5.1 #1
IkeM-Ldev-containers.yml
on: push
Annotations
16 errors and 5 warnings
|
Build and Scan Container Images (3.14)
Canceling since a higher priority waiting request for container-registry exists
|
|
Build and Scan Container Images (3.14)
Path does not exist: trivy-results-py3.14.sarif
|
|
Build and Scan Container Images (3.14)
Process completed with exit code 1.
|
|
Build and Scan Container Images (3.13)
Canceling since a higher priority waiting request for container-registry exists
|
|
Build and Scan Container Images (3.13)
Path does not exist: trivy-results-py3.13.sarif
|
|
Build and Scan Container Images (3.13)
The operation was canceled.
|
|
Build and Scan Container Images (3.11)
Canceling since a higher priority waiting request for container-registry exists
|
|
Build and Scan Container Images (3.11)
Path does not exist: trivy-results-py3.11.sarif
|
|
Build and Scan Container Images (3.11)
The operation was canceled.
|
|
Build and Scan Container Images (3.10)
Canceling since a higher priority waiting request for container-registry exists
|
|
Build and Scan Container Images (3.10)
Path does not exist: trivy-results-py3.10.sarif
|
|
Build and Scan Container Images (3.10)
The operation was canceled.
|
|
Build and Scan Container Images (3.12)
Canceling since a higher priority waiting request for container-registry exists
|
|
Build and Scan Container Images (3.12)
Path does not exist: trivy-results-py3.12.sarif
|
|
Build and Scan Container Images (3.12)
The operation was canceled.
|
|
Container Build
Canceling since a higher priority waiting request for container-registry exists
|
|
Build and Scan Container Images (3.14)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: astral-sh/setup-uv@v6. 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/
|
|
Build and Scan Container Images (3.13)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: astral-sh/setup-uv@v6. 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/
|
|
Build and Scan Container Images (3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: astral-sh/setup-uv@v6. 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/
|
|
Build and Scan Container Images (3.10)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: astral-sh/setup-uv@v6. 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/
|
|
Build and Scan Container Images (3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: astral-sh/setup-uv@v6. 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/
|