Feature/mcp registry submissions (#673) #684
general-kroll-4-lifebuild.yml
on: push
Matrix: Docker Build
Linux Build
36s
Test Python Package Build
47s
Windows Build
36s
Linux arm64 Build
48s
MacOS Build
42s
MacOS ARM Build
50s
dockermerge
0s
Annotations
22 errors and 15 warnings
|
Linux Build
The run was canceled by @general-kroll-4-life.
|
|
Linux Build
The operation was canceled.
|
|
Docker Build (linux/arm64)
The run was canceled by @general-kroll-4-life.
|
|
Docker Build (linux/arm64)
The operation was canceled.
|
|
Windows Build
The run was canceled by @general-kroll-4-life.
|
|
Windows Build
Process completed with exit code 1.
|
|
Windows Build
The operation was canceled.
|
|
Docker Build (linux/amd64)
The run was canceled by @general-kroll-4-life.
|
|
Docker Build (linux/amd64)
The operation was canceled.
|
|
MacOS Build
The run was canceled by @general-kroll-4-life.
|
|
MacOS Build
Process completed with exit code 1.
|
|
MacOS Build
The operation was canceled.
|
|
Test Python Package Build
The run was canceled by @general-kroll-4-life.
|
|
Test Python Package Build
The operation was canceled.
|
|
Linux arm64 Build
The run was canceled by @general-kroll-4-life.
|
|
Linux arm64 Build
Process completed with exit code 1.
|
|
Linux arm64 Build
Process completed with exit code 1.
|
|
Linux arm64 Build
Process completed with exit code 1.
|
|
Linux arm64 Build
The operation was canceled.
|
|
MacOS ARM Build
The run was canceled by @general-kroll-4-life.
|
|
MacOS ARM Build
The operation was canceled.
|
|
Build
The run was canceled by @general-kroll-4-life.
|
|
Linux Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.1.1, actions/setup-go@v5.0.0, actions/setup-python@v5.0.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Linux Build
Failed to restore: Cache service responded with 400
|
|
Linux Build
Failed to restore: Cache service responded with 400
|
|
Docker Build (linux/arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.1.1, docker/metadata-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Windows Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.1.1, actions/setup-go@v5.0.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Docker Build (linux/amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.1.1, docker/metadata-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
MacOS Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.1.1, actions/setup-go@v5.0.0, actions/upload-artifact@v4.3.1. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Test Python Package Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.1.1, actions/setup-python@v5.0.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Test Python Package Build
Failed to restore: Cache service responded with 400
|
|
Linux arm64 Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.1.1, actions/setup-go@v5.0.0, actions/setup-python@v5.0.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Linux arm64 Build
Failed to restore: Cache service responded with 400
|
|
Linux arm64 Build
Failed to restore: Cache service responded with 400
|
|
MacOS ARM Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.1.1, actions/setup-go@v5.0.0, actions/setup-python@v5.0.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
MacOS ARM Build
Failed to restore: Cache service responded with 400
|
|
MacOS ARM Build
Failed to restore: Cache service responded with 400
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
stackql_darwin_amd64_robot_reports
|
150 Bytes |
sha256:00c3be74be90dbf6c8524df1cbbb544f8d76a570da4a852f64b9e2dcabe95e63
|
|
|
stackql_darwin_amd64_robot_tmp
|
149 Bytes |
sha256:3515ec8bfcf4e00d52fb597a739bb9ad1429ad857b1044f491e8de386f52ae47
|
|