Skip to content

fix: correct COPY paths in credential sidecar Dockerfiles for CI build context #4738

fix: correct COPY paths in credential sidecar Dockerfiles for CI build context

fix: correct COPY paths in credential sidecar Dockerfiles for CI build context #4738

Triggered via pull request June 1, 2026 20:27
Status Failure
Total duration 10m 20s
Artifacts 28

components-build-deploy.yml

on: pull_request
build-matrix
5s
build-matrix
Matrix: build
deploy-rhoai-mlflow
0s
deploy-rhoai-mlflow
Matrix: merge-manifests
update-rbac-and-crd
0s
update-rbac-and-crd
deploy-to-openshift
0s
deploy-to-openshift
deploy-with-disptach
0s
deploy-with-disptach
Fit to window
Zoom out
Zoom in

Annotations

15 errors and 32 warnings
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-1627-amd64: 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-1627-amd64: 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-1627-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, 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-1627-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-1627-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-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-1627-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-1627-arm64: denied: System is currently read-only. Pulls will succeed but all write operations are currently suspended.
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 push quay.io/ambient_code/vteam_credential_jira:pr-1627-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 push quay.io/ambient_code/vteam_credential_google:pr-1627-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-1627-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, credential-jira, ./components, quay.io/ambient_code/...
buildx failed with: ERROR: failed to build: failed to solve: failed to push quay.io/ambient_code/vteam_credential_jira:pr-1627-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, credential-google, ./components, quay.io/ambient_cod...
buildx failed with: ERROR: failed to build: failed to solve: failed to push quay.io/ambient_code/vteam_credential_google:pr-1627-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-1627-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-1627-arm64: 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-1627-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...
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-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/
Sensitive data should not be used in the ARG or ENV commands: components/credential-sidecars/k8s/Dockerfile#L26
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "CREDENTIAL_PROVIDER") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
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-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-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, 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-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-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-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-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-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, 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-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-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/
Sensitive data should not be used in the ARG or ENV commands: components/credential-sidecars/github/Dockerfile#L24
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "CREDENTIAL_PROVIDER") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
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/
Sensitive data should not be used in the ARG or ENV commands: components/credential-sidecars/k8s/Dockerfile#L26
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "CREDENTIAL_PROVIDER") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
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, 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, 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, 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-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, 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, 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/
Sensitive data should not be used in the ARG or ENV commands: components/credential-sidecars/github/Dockerfile#L24
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "CREDENTIAL_PROVIDER") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
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-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, 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~087C4N.dockerbuild
44.1 KB
sha256:9e5c81b9f72e70d845569a34d45d4c1064be05f429e53d384294c5872fe18dd4
ambient-code~platform~0QZYQ6.dockerbuild
53 KB
sha256:55d33a2be9e6309ceb8f355a92b8470da018abfda71189f816f2602e22c90f85
ambient-code~platform~5P0QC1.dockerbuild
50.5 KB
sha256:0c4644a04ea5f92e66f9214a2c7afc0a767d5e69fbfbb22706ba1b677e8891a1
ambient-code~platform~7Q416I.dockerbuild
84 KB
sha256:3c45307b92d6e4c808d9be3b67e0b069f5d0acbf49b201c84ad5cbbf92f244a5
ambient-code~platform~7S8C9P.dockerbuild
36.2 KB
sha256:20b6046caa5e5b163a3fa22c5ac2fc0062fcea0b09dfc0befc1319975d0a58bb
ambient-code~platform~A45GZX.dockerbuild
44.5 KB
sha256:21d265f7ed58714f597dbbe99cb998076736ae2598ffe086f832e6125cdb7a58
ambient-code~platform~BMODGR.dockerbuild
65.6 KB
sha256:eb351dde8c150e6ab865adf3010e8aacebdf2e57f07a0998e2fbd9ca17fcb614
ambient-code~platform~CO1OLD.dockerbuild
56.5 KB
sha256:55dd910748474f0ec37abda10035b4644f4aa6d107dc88ad0141dfd9a6e5f5ef
ambient-code~platform~G5VFJU.dockerbuild
35.8 KB
sha256:0c599254b3ffdd52b08d9b0d152a1cc4cb6f8b134730ca3af07368fd31005a3b
ambient-code~platform~H7FLUU.dockerbuild
31.9 KB
sha256:2ff98d1a68e7778d59c6c199b7d1a245cc6af81ec9f71c74cdf62bf302100449
ambient-code~platform~KI12JS.dockerbuild
31.8 KB
sha256:02af6153ed15f27e1435b81de8883fddf199062d4a3c8e340f407468f742cee3
ambient-code~platform~KXA7QA.dockerbuild
60.5 KB
sha256:dc4b476e3102ccf5b2aea9efd3ac791885e4ffae94e4380c186b3f1ca962bc7e
ambient-code~platform~NH4EL0.dockerbuild
97.5 KB
sha256:9a94afc7d0864332b4d6ec63deff5445f99287da7277a4f59ecf56f8dbb93455
ambient-code~platform~NQPJ7Z.dockerbuild
62 KB
sha256:095617beff01ffd246bfa2fbd63deccb450735c690cf302c9f44aeceb3aeb78b
ambient-code~platform~O2STI8.dockerbuild
43.6 KB
sha256:7f35fafa63642e050d6ddb1985691314e05ec8274c8290a29a8659d2c83b3ca4
ambient-code~platform~OFSQ3T.dockerbuild
49 KB
sha256:ad41ecb0f607b82733831341d4e232b9d53e236b7e621d1e38515b4fab06a16e
ambient-code~platform~PE18MF.dockerbuild
52.9 KB
sha256:95b30d737331d2ed54a83d6c1b527379ba6241c7e876548fe0a7bc4d368331c6
ambient-code~platform~S0B8E1.dockerbuild
61 KB
sha256:22e25d9a70e77beefb07eee59fca6c873cfdb8dbd3d95680b21439f534b436ac
ambient-code~platform~T2J8VU.dockerbuild
48.1 KB
sha256:0004c33e52c3bd912402532faea2965591c560cc3becc36746a7076b5e03dc0d
ambient-code~platform~TPRRMW.dockerbuild
41.8 KB
sha256:76f86ae23113e948b244d01b90c47c9d0d1987d3b48191c14cfd25a39a964cb9
ambient-code~platform~U1ETNA.dockerbuild
60.9 KB
sha256:a9f028c17d8cef96146575be524c2ce8a4c649d22865fbe9095eb09255d77efd
ambient-code~platform~U3GTYT.dockerbuild
50.1 KB
sha256:d55a395b1da74e4d61e0ca219f61b072be278449d8d10e933e52cd50d60146ad
ambient-code~platform~UZ8SIJ.dockerbuild
83.2 KB
sha256:ded81be0a9d86b1ccdd2864e7926a034482ca08950b6f7050426c00b0fd1503b
ambient-code~platform~X477LJ.dockerbuild
52 KB
sha256:8407ef096a39eb04654a33fa2d64d9b13fdb9e2a42c2032e18bb8355d43bd5e7
ambient-code~platform~Y1DSEE.dockerbuild
42.8 KB
sha256:6a840a02cab3515a7681b4c3c3eb8abc64f536e0872d73437eb6aad6a1b7ff6a
ambient-code~platform~YA7LM2.dockerbuild
50.2 KB
sha256:e3dacde87692bfdc785ddf14127152921d124733a6787608556e7d72e678418d
ambient-code~platform~Z46MZ6.dockerbuild
96.2 KB
sha256:c0199d54e092766fa6758edcbed3dc3b0bbe57d47e296f08e5e4f1f21bf8dbb6
ambient-code~platform~ZN27LF.dockerbuild
38.2 KB
sha256:e55543291cdad52fa4c77fd04f055ea210e27cd6af7437bd740027f1b4dfe927