Skip to content

feat(runner): add Claude Code plugin loading via PLUGINS_JSON #3360

feat(runner): add Claude Code plugin loading via PLUGINS_JSON

feat(runner): add Claude Code plugin loading via PLUGINS_JSON #3360

Triggered via pull request March 30, 2026 22:00
Status Failure
Total duration 6m 30s
Artifacts 14

components-build-deploy.yml

on: pull_request
detect-changes
6s
detect-changes
Matrix: build
Matrix: merge-manifests
update-rbac-and-crd
update-rbac-and-crd
deploy-to-openshift
deploy-to-openshift
deploy-with-disptach
deploy-with-disptach
Fit to window
Zoom out
Zoom in

Annotations

14 errors and 14 warnings
build (ubuntu-24.04-arm, linux/arm64, arm64, state-sync, ./components/runners/state-sync, quay.io...
buildx failed with: ERROR: failed to build: failed to solve: failed to push quay.io/ambient_code/vteam_state_sync:pr-1109-arm64: denied: System is currently read-only. Pulls will succeed but all write operations are currently suspended.
build (ubuntu-latest, linux/amd64, amd64, state-sync, ./components/runners/state-sync, quay.io/am...
buildx failed with: ERROR: failed to build: failed to solve: failed to push quay.io/ambient_code/vteam_state_sync:pr-1109-amd64: denied: System is currently read-only. Pulls will succeed but all write operations are currently suspended.
build (ubuntu-latest, linux/amd64, amd64, public-api, ./components/public-api, quay.io/ambient_co...
buildx failed with: ERROR: failed to build: failed to solve: failed to push quay.io/ambient_code/vteam_public_api:pr-1109-amd64: denied: System is currently read-only. Pulls will succeed but all write operations are currently suspended.
build (ubuntu-latest, linux/amd64, amd64, ambient-api-server, ./components/ambient-api-server, qu...
buildx failed with: ERROR: failed to build: failed to solve: failed to push quay.io/ambient_code/vteam_api_server:pr-1109-amd64: denied: System is currently read-only. Pulls will succeed but all write operations are currently suspended.
build (ubuntu-latest, linux/amd64, amd64, frontend, ./components/frontend, quay.io/ambient_code/v...
buildx failed with: ERROR: failed to build: failed to solve: failed to push quay.io/ambient_code/vteam_frontend:pr-1109-amd64: denied: System is currently read-only. Pulls will succeed but all write operations are currently suspended.
build (ubuntu-24.04-arm, linux/arm64, arm64, public-api, ./components/public-api, quay.io/ambient...
buildx failed with: ERROR: failed to build: failed to solve: failed to push quay.io/ambient_code/vteam_public_api:pr-1109-arm64: denied: System is currently read-only. Pulls will succeed but all write operations are currently suspended.
build (ubuntu-24.04-arm, linux/arm64, arm64, operator, ./components/operator, quay.io/ambient_cod...
buildx failed with: ERROR: failed to build: failed to solve: failed to push quay.io/ambient_code/vteam_operator:pr-1109-arm64: denied: System is currently read-only. Pulls will succeed but all write operations are currently suspended.
build (ubuntu-24.04-arm, linux/arm64, arm64, ambient-api-server, ./components/ambient-api-server,...
buildx failed with: ERROR: failed to build: failed to solve: failed to push quay.io/ambient_code/vteam_api_server:pr-1109-arm64: denied: System is currently read-only. Pulls will succeed but all write operations are currently suspended.
build (ubuntu-latest, linux/amd64, amd64, operator, ./components/operator, quay.io/ambient_code/v...
buildx failed with: ERROR: failed to build: failed to solve: failed to push quay.io/ambient_code/vteam_operator:pr-1109-amd64: denied: System is currently read-only. Pulls will succeed but all write operations are currently suspended.
build (ubuntu-latest, linux/amd64, amd64, backend, ./components/backend, quay.io/ambient_code/vte...
buildx failed with: ERROR: failed to build: failed to solve: failed to push quay.io/ambient_code/vteam_backend:pr-1109-amd64: denied: System is currently read-only. Pulls will succeed but all write operations are currently suspended.
build (ubuntu-24.04-arm, linux/arm64, arm64, backend, ./components/backend, quay.io/ambient_code/...
buildx failed with: ERROR: failed to build: failed to solve: failed to push quay.io/ambient_code/vteam_backend:pr-1109-arm64: denied: System is currently read-only. Pulls will succeed but all write operations are currently suspended.
build (ubuntu-24.04-arm, linux/arm64, arm64, frontend, ./components/frontend, quay.io/ambient_cod...
buildx failed with: ERROR: failed to build: failed to solve: failed to push quay.io/ambient_code/vteam_frontend:pr-1109-arm64: denied: System is currently read-only. Pulls will succeed but all write operations are currently suspended.
build (ubuntu-latest, linux/amd64, amd64, ambient-runner, ./components/runners, quay.io/ambient_c...
buildx failed with: ERROR: failed to build: failed to solve: failed to push quay.io/ambient_code/vteam_claude_runner:pr-1109-amd64: denied: System is currently read-only. Pulls will succeed but all write operations are currently suspended.
build (ubuntu-24.04-arm, linux/arm64, arm64, ambient-runner, ./components/runners, quay.io/ambien...
buildx failed with: ERROR: failed to build: failed to solve: failed to push quay.io/ambient_code/vteam_claude_runner:pr-1109-arm64: denied: System is currently read-only. Pulls will succeed but all write operations are currently suspended.
build (ubuntu-24.04-arm, linux/arm64, arm64, state-sync, ./components/runners/state-sync, quay.io...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3, docker/setup-buildx-action@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/
build (ubuntu-latest, linux/amd64, amd64, state-sync, ./components/runners/state-sync, quay.io/am...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3, docker/setup-buildx-action@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/
build (ubuntu-latest, linux/amd64, amd64, public-api, ./components/public-api, quay.io/ambient_co...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3, docker/setup-buildx-action@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/
build (ubuntu-latest, linux/amd64, amd64, ambient-api-server, ./components/ambient-api-server, qu...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3, docker/setup-buildx-action@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/
build (ubuntu-latest, linux/amd64, amd64, frontend, ./components/frontend, quay.io/ambient_code/v...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3, docker/setup-buildx-action@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/
build (ubuntu-24.04-arm, linux/arm64, arm64, public-api, ./components/public-api, quay.io/ambient...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3, docker/setup-buildx-action@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/
build (ubuntu-24.04-arm, linux/arm64, arm64, operator, ./components/operator, quay.io/ambient_cod...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3, docker/setup-buildx-action@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/
build (ubuntu-24.04-arm, linux/arm64, arm64, ambient-api-server, ./components/ambient-api-server,...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3, docker/setup-buildx-action@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/
build (ubuntu-latest, linux/amd64, amd64, operator, ./components/operator, quay.io/ambient_code/v...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3, docker/setup-buildx-action@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/
build (ubuntu-latest, linux/amd64, amd64, backend, ./components/backend, quay.io/ambient_code/vte...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3, docker/setup-buildx-action@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/
build (ubuntu-24.04-arm, linux/arm64, arm64, backend, ./components/backend, quay.io/ambient_code/...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3, docker/setup-buildx-action@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/
build (ubuntu-24.04-arm, linux/arm64, arm64, frontend, ./components/frontend, quay.io/ambient_cod...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3, docker/setup-buildx-action@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/
build (ubuntu-latest, linux/amd64, amd64, ambient-runner, ./components/runners, quay.io/ambient_c...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3, docker/setup-buildx-action@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/
build (ubuntu-24.04-arm, linux/arm64, arm64, ambient-runner, ./components/runners, quay.io/ambien...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3, docker/setup-buildx-action@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/

Artifacts

Produced during runtime
Name Size Digest
ambient-code~platform~1XOQNJ.dockerbuild
53 KB
sha256:f1e596d45bd814e67fc927cf78ba06630bad579a59d869d55768a6f7f535e4e9
ambient-code~platform~BTNJLS.dockerbuild
46.4 KB
sha256:190108e4f0ac2257ace8d215aeb700766989fd7c343619ab827ad42a04e24a87
ambient-code~platform~ID06HQ.dockerbuild
44.7 KB
sha256:e7e47f8a2645dc764ca5f3264aa7e9e13d44aa2a59b123aed5c85b246198a58c
ambient-code~platform~JMTDVD.dockerbuild
35.5 KB
sha256:e5f9d5adffef7d42f24f56fd3b58ca1069cacd5ef426ac6caf6ae74351059301
ambient-code~platform~NNDS8O.dockerbuild
76.1 KB
sha256:73138e825492c690fbced6fb42ba4d0ad0ea98c3e032ccd1ae86cef4e8c93215
ambient-code~platform~NR0FLF.dockerbuild
50.4 KB
sha256:18762d3517ca62cf8dd9b0d7d60b359741692001a829255136cd3dfae4cc7613
ambient-code~platform~OYO35Z.dockerbuild
43.5 KB
sha256:2b5cec92e0ff45380b8f9d47f9461cb9c70bf6b3951e1a74c98a9a0f11e0cb42
ambient-code~platform~PQS0NT.dockerbuild
47.1 KB
sha256:6c3d4ed648d7a4b2258979b58a4ff07d7c5c4ec95b052f1719d68d7f519cbb63
ambient-code~platform~PRYYPT.dockerbuild
49.8 KB
sha256:8629eae03bddd2d0876e075305ba763fc1d258b3a0b9aafcb79b27074990a1bc
ambient-code~platform~PYGH1U.dockerbuild
75.1 KB
sha256:6dd278d71baf49ff642bf590b9eab8ad5cf2e1034ad8b0ab6dada188eb5d2e14
ambient-code~platform~R3PVQC.dockerbuild
53.2 KB
sha256:10f68b9bae02cc6681d6de9e2649d206693c1429c5845499c3e49a3e0f3ec4e0
ambient-code~platform~RP8M4D.dockerbuild
50 KB
sha256:4e1c342bf64c5cbd320c9ef55afc147fe14d5ace19e541b160f335deb649bcc5
ambient-code~platform~WFE0VP.dockerbuild
32.2 KB
sha256:1cb2e1b7ed961ef178c9ec9f1127e6c262dac9ca84fd8efe10cd498ea196f097
ambient-code~platform~X152EI.dockerbuild
49.7 KB
sha256:d1a30dbfacb9f0a603f4e4256ee5a3313113d3d7a287f69c214f811cf1366b2f