Skip to content
Deploy backend to Cloud Run

fix: Cloud Run deploy with GCS auth, env vars, and branch trigger #1

Sign in to view logs

fix: Cloud Run deploy with GCS auth, env vars, and branch trigger

fix: Cloud Run deploy with GCS auth, env vars, and branch trigger #1

Triggered via push March 26, 2026 00:27
@SiriappsSiriapps
pushed d6f512c
feat/model-training
Status Failure
Total duration 10s
Artifacts –

deploy.yml

on: push
deploy
6s
deploy
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 warning
deploy
google-github-actions/auth failed with: the GitHub Action workflow must specify exactly one of "workload_identity_provider" or "credentials_json"! If you are specifying input values via GitHub secrets, ensure the secret is being injected into the environment. By default, secrets are not passed to workflows triggered from forks, including Dependabot.
deploy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, google-github-actions/auth@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/