Skip to content

Deploy to Staging

Deploy to Staging #3

Manually triggered May 6, 2026 13:05
Status Failure
Total duration 1m 22s
Artifacts 1

staging-deploy.yml

on: workflow_dispatch
Matrix: Test
deploy  /  ...  /  build
deploy / deploy-staging / build-gcp / build
deploy  /  ...  /  build
deploy / deploy-staging / build-aws / build
deploy  /  ...  /  deploy
deploy / deploy-staging / deploy-gcp-staging / deploy
deploy  /  ...  /  deploy
deploy / deploy-staging / deploy-staging-aws / deploy
deploy  /  ...  /  run_test
deploy / 🧪 Run Staging Validation Tests / run_test
deploy  /  🚫 Await Manual Approval (Tests Failed)
0s
deploy / 🚫 Await Manual Approval (Tests Failed)
deploy  /  ...  /  Checkout Code
deploy / deploy-production / Checkout Code
deploy  /  ...  /  Determine Version
deploy / deploy-production / Determine Version
deploy  /  ...  /  Create Git Tag
deploy / deploy-production / Create Git Tag
deploy  /  ...  /  build
deploy / deploy-production / build-gcp / build
deploy  /  ...  /  build
deploy / deploy-production / build-aws / build
deploy  /  ...  /  Create GitHub Release
deploy / deploy-production / Create GitHub Release
deploy  /  ...  /  deploy
deploy / deploy-production / deploy-gcp-production / deploy
deploy  /  ...  /  deploy
deploy / deploy-production / deploy-production-aws / deploy
Fit to window
Zoom out
Zoom in

Annotations

1 error and 3 warnings
deploy / deploy-staging / build-aws / Build (staging)
buildx failed with: ERROR: failed to build: unable to prepare context: path "./app" not found
Test (3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5, actions/upload-artifact@v4. 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/
deploy / Setup
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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/
deploy / deploy-staging / build-aws / Build (staging)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, aws-actions/configure-aws-credentials@v4, docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, 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
test-results-3.12
508 Bytes
sha256:eb692bedb702fd930a826f1d6fbeb44153d10ff152099b21b0c8ed6a38b55fda