Skip to content

feat: credential MCP sidecar isolation with CI/CD pipeline support #4721

feat: credential MCP sidecar isolation with CI/CD pipeline support

feat: credential MCP sidecar isolation with CI/CD pipeline support #4721

Triggered via pull request June 1, 2026 14:58
Status Failure
Total duration 8m 5s
Artifacts 28

components-build-deploy.yml

on: pull_request
build-matrix
2s
build-matrix
Matrix: build
deploy-rhoai-mlflow
0s
deploy-rhoai-mlflow
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

28 errors and 28 warnings
build (ubuntu-latest, linux/amd64, amd64, credential-k8s, ./components, quay.io/ambient_code/vtea...
buildx failed with: ERROR: failed to build: failed to solve: failed to compute cache key: failed to calculate checksum of ref dupdgq93autd093vfhuwdy5op::vuz0v68tc7rtv84apas75fh6f: "/components/ambient-mcp": not found
build (ubuntu-latest, linux/amd64, amd64, credential-github, ./components, quay.io/ambient_code/v...
buildx failed with: ERROR: failed to build: failed to solve: failed to compute cache key: failed to calculate checksum of ref 0ex76tcog2bmdr88eyz0bnjrv::rddgiwuppz0g2deaa0oj39xbz: "/components/ambient-mcp": not found
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-1623-amd64: denied: System is currently read-only. Pulls will succeed but all write operations are currently suspended.
build (ubuntu-latest, linux/amd64, amd64, credential-google, ./components, quay.io/ambient_code/v...
buildx failed with: ERROR: failed to build: failed to solve: failed to compute cache key: failed to calculate checksum of ref vbxtfwbfi29iljz9j2dv67awo::ryw3ni1mkuxww6mcw1bfkiflq: "/components/ambient-mcp": not found
build (ubuntu-latest, linux/amd64, amd64, credential-jira, ./components, quay.io/ambient_code/vte...
buildx failed with: ERROR: failed to build: failed to solve: failed to compute cache key: failed to calculate checksum of ref 9yfkr9ezm8kbz8a4hpxl777x9::dfl61bz8j2rkhj6phb7tl760j: "/components/ambient-mcp": not found
build (ubuntu-24.04-arm, linux/arm64, arm64, credential-jira, ./components, quay.io/ambient_code/...
buildx failed with: ERROR: failed to build: failed to solve: failed to compute cache key: failed to calculate checksum of ref bo0w08birsxms0df9rvt5bapk::k88bx6z67ecfalv5015hbplar: "/components/ambient-mcp": not found
build (ubuntu-24.04-arm, linux/arm64, arm64, credential-google, ./components, quay.io/ambient_cod...
buildx failed with: ERROR: failed to build: failed to solve: failed to compute cache key: failed to calculate checksum of ref j9djww2yd9iiowm1vdb0ldcf7::2u39qvdqnrdt98bz2z2jn2rhq: "/components/ambient-mcp": not found
build (ubuntu-24.04-arm, linux/arm64, arm64, credential-k8s, ./components, quay.io/ambient_code/v...
buildx failed with: ERROR: failed to build: failed to solve: failed to compute cache key: failed to calculate checksum of ref sf963yp9dah7lh13dhipixwdh::pgixkr50vdp48s4ggyshn3pny: "/components/ambient-mcp": not found
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-1623-arm64: denied: System is currently read-only. Pulls will succeed but all write operations are currently suspended.
build (ubuntu-latest, linux/amd64, amd64, ambient-mcp, ./components/ambient-mcp, quay.io/ambient_...
buildx failed with: ERROR: failed to build: failed to solve: failed to push quay.io/ambient_code/vteam_mcp:pr-1623-amd64: denied: System is currently read-only. Pulls will succeed but all write operations are currently suspended.
build (ubuntu-latest, linux/amd64, amd64, ambient-control-plane, ./components, quay.io/ambient_co...
buildx failed with: ERROR: failed to build: failed to solve: failed to push quay.io/ambient_code/vteam_control_plane:pr-1623-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, credential-github, ./components, quay.io/ambient_cod...
buildx failed with: ERROR: failed to build: failed to solve: failed to compute cache key: failed to calculate checksum of ref utl6xj0odkij81w2ngsjo9g0r::nu3yy5m08bysr4xb3pp50mkbn: "/components/ambient-mcp": not found
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-1623-arm64: 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-1623-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-control-plane, ./components, quay.io/ambient...
buildx failed with: ERROR: failed to build: failed to solve: failed to push quay.io/ambient_code/vteam_control_plane:pr-1623-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, 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-1623-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-ui, ./components, quay.io/ambient_code/vteam...
buildx failed with: ERROR: failed to build: failed to solve: failed to push quay.io/ambient_code/vteam_ambient_ui:pr-1623-arm64: 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-1623-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-1623-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-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-1623-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-1623-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-1623-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-1623-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-1623-arm64: denied: System is currently read-only. Pulls will succeed but all write operations are currently suspended.
build (ubuntu-latest, linux/amd64, amd64, ambient-ui, ./components, quay.io/ambient_code/vteam_am...
buildx failed with: ERROR: failed to build: failed to solve: failed to push quay.io/ambient_code/vteam_ambient_ui:pr-1623-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-mcp, ./components/ambient-mcp, quay.io/ambie...
buildx failed with: ERROR: failed to build: failed to solve: failed to push quay.io/ambient_code/vteam_mcp:pr-1623-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/ambient-runner, qu...
buildx failed with: ERROR: failed to build: failed to solve: failed to push quay.io/ambient_code/vteam_claude_runner:pr-1623-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/ambient-runner,...
buildx failed with: ERROR: failed to build: failed to solve: failed to push quay.io/ambient_code/vteam_claude_runner:pr-1623-arm64: denied: System is currently read-only. Pulls will succeed but all write operations are currently suspended.
build (ubuntu-latest, linux/amd64, amd64, credential-k8s, ./components, quay.io/ambient_code/vtea...
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 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/
build (ubuntu-latest, linux/amd64, amd64, credential-github, ./components, 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 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/
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 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/
build (ubuntu-latest, linux/amd64, amd64, credential-google, ./components, 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 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/
build (ubuntu-latest, linux/amd64, amd64, credential-jira, ./components, 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 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/
build (ubuntu-24.04-arm, linux/arm64, arm64, credential-jira, ./components, 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 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/
build (ubuntu-24.04-arm, linux/arm64, arm64, credential-google, ./components, 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 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/
build (ubuntu-24.04-arm, linux/arm64, arm64, credential-k8s, ./components, 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 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/
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 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/
build (ubuntu-latest, linux/amd64, amd64, ambient-mcp, ./components/ambient-mcp, 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 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/
build (ubuntu-latest, linux/amd64, amd64, ambient-control-plane, ./components, 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 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/
build (ubuntu-24.04-arm, linux/arm64, arm64, credential-github, ./components, 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 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/
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 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/
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 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/
build (ubuntu-24.04-arm, linux/arm64, arm64, ambient-control-plane, ./components, 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 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/
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 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/
build (ubuntu-24.04-arm, linux/arm64, arm64, ambient-ui, ./components, quay.io/ambient_code/vteam...
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 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/
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 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/
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 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/
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 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/
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 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/
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 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/
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 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/
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 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/
build (ubuntu-latest, linux/amd64, amd64, ambient-ui, ./components, quay.io/ambient_code/vteam_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 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/
build (ubuntu-24.04-arm, linux/arm64, arm64, ambient-mcp, ./components/ambient-mcp, quay.io/ambie...
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 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/
build (ubuntu-latest, linux/amd64, amd64, ambient-runner, ./components/runners/ambient-runner, 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 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/
build (ubuntu-24.04-arm, linux/arm64, arm64, ambient-runner, ./components/runners/ambient-runner,...
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 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/

Artifacts

Produced during runtime
Name Size Digest
ambient-code~platform~4S2KAC.dockerbuild
32.6 KB
sha256:31b79db00fdda511006e5e212edcacfb489ad201f55078a5f65a35efec4b11ea
ambient-code~platform~ARVD4S.dockerbuild
48.1 KB
sha256:6281ce279594ab0dae85c564d652d18d59e94c519deadf37caa649a3571e5d08
ambient-code~platform~C7HQ0C.dockerbuild
15.7 KB
sha256:54b267edd96c62719c88620eefb0262c8bc9b1ddd6fc1f0d107811cb1f30bf8e
ambient-code~platform~CG2UFM.dockerbuild
52.9 KB
sha256:655f0eb7367ff16bce3dbab3123eeeb89fe50f498f97f2044838163912376d6c
ambient-code~platform~CQRPCR.dockerbuild
17.1 KB
sha256:ad49919144205d15962eda2eb3f73806e85fd891a2302e4da53a9fb0ca34a30f
ambient-code~platform~CWVYDN.dockerbuild
43.2 KB
sha256:d09406a456ab3df849bf2e4ea01e4ec5245ac45a103de8c8e1bdb815cf763088
ambient-code~platform~GB471F.dockerbuild
15.5 KB
sha256:5fa41208748ed29032ad6e887882bfbc164663e29e85c65e7a9fcbe43d5b173a
ambient-code~platform~GRKV7I.dockerbuild
73.9 KB
sha256:c774447752614b253fa7dea4f869a88e183a6cecd8397f25f48d3c80a9553980
ambient-code~platform~HD71PH.dockerbuild
19.1 KB
sha256:6390fff6d4f14039a495926c4a8761014e02a333b27bbe9d426c9974d4682323
ambient-code~platform~K1LQP2.dockerbuild
49.6 KB
sha256:ba4475459e10e37170e1433814259a05d59d20fc0da7dfceb7f5959395b85d3d
ambient-code~platform~K4Z7SS.dockerbuild
19.2 KB
sha256:c072fa70b05e2757d79e925c76d8ef6f013fbaabaf69b82698e1c78100f4a951
ambient-code~platform~LP8ZE8.dockerbuild
32.6 KB
sha256:fded3540160f8800c19ef64c225e25c62188fa5e24d21b195113631a41e87473
ambient-code~platform~M6UTD7.dockerbuild
44.4 KB
sha256:0686297fa5bbfa30bf92c6472793e1483286d2c8c9ab4c049bd10b5389a577bb
ambient-code~platform~MJN062.dockerbuild
15.6 KB
sha256:63e48d47808db21de5f6c93e43634912611996637c4d50711c89ef9d91673264
ambient-code~platform~OY7U1A.dockerbuild
45.5 KB
sha256:9ba13da63033ec79e1ebf02183b95d387a9796fe9e1e9aecb86a54799de76198
ambient-code~platform~OZTDS7.dockerbuild
44.9 KB
sha256:1298b36539d1aa08f98962e129ac76e2e4f696a0b2c4978f7fba10aa6630c83b
ambient-code~platform~PFVOYF.dockerbuild
74.2 KB
sha256:2e13a296213a654e2bdc6a33181805ec7a9d9d53d625334f2eb7c7f8558142a4
ambient-code~platform~RCODXH.dockerbuild
44.5 KB
sha256:9cedcba7051dc0b954a8767c32a13a0f9698f424bb8f1d22d55cc6191424579b
ambient-code~platform~RP4UGZ.dockerbuild
53.3 KB
sha256:49db176623ff497b55bad17ec57b22078640c47c0276857908bf687864ceb72f
ambient-code~platform~SOFUNR.dockerbuild
48.3 KB
sha256:5767749b5e942c6f7ae23600cd92bb29df9d44a309339266c740266f16f5d00d
ambient-code~platform~T0PUCB.dockerbuild
49.3 KB
sha256:86fd94ba2659a7aec54dc27f763e5757f6463aaa1b130c8a8ae9dbdda30dbfd4
ambient-code~platform~TWOIG5.dockerbuild
83.7 KB
sha256:86b9a8134065ca0ab77e3c49c1ff15b71914c24084ad7d68c0e6bcacf2782707
ambient-code~platform~UYBVNR.dockerbuild
82.7 KB
sha256:616cba6d9848b9dcff999e34c25376337a3e062c1240b1deea98263f59e8951a
ambient-code~platform~WEAMMD.dockerbuild
45.6 KB
sha256:a9589158c28a036697a883f49ea32d260fe7b1e1c9e0da39d5452126210071c4
ambient-code~platform~YB3YEH.dockerbuild
17 KB
sha256:b26977d4de7138209b098554ef62f965efac25304653fff659b4d7a69c728d18
ambient-code~platform~YV5I5J.dockerbuild
43.3 KB
sha256:d6c66f6def918152ea94d2175d65350047352d53e00bc152ed37be6dc2b053f6
ambient-code~platform~Z3WRAX.dockerbuild
16.8 KB
sha256:b24b09f2a6aaf3c66a130c790d7e4c2a84c6796c8753c11f4ea0512f7d544888
ambient-code~platform~Z99M46.dockerbuild
44.5 KB
sha256:98a7dcb13b35fab5b0a8cc0d543872aefcd188f68443368c7681de283b893bc8