Skip to content

Update docker image to 29.2.1 #106

Update docker image to 29.2.1

Update docker image to 29.2.1 #106

Re-run triggered February 13, 2026 06:08
Status Failure
Total duration 47s
Artifacts

build_and_push.yaml

on: pull_request
Build & push - with workload identity
4s
Build & push - with workload identity
Build & push - with service account
4s
Build & push - with service account
Build & push - without gcloud auth action
22s
Build & push - without gcloud auth action
Push only - with workload identity
16s
Push only - with workload identity
Matrix: Test images from registry
Clean up images
16s
Clean up images
Fit to window
Zoom out
Zoom in

Annotations

4 errors
Build & push - with workload identity
google-github-actions/auth failed with: gitHub Actions did not inject $ACTIONS_ID_TOKEN_REQUEST_TOKEN or $ACTIONS_ID_TOKEN_REQUEST_URL into this job. This most likely means the GitHub Actions workflow permissions are incorrect, or this job is being run from a fork. For more information, please see https://docs.github.com/en/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token
Build & push - with service account
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.
Push only - with workload identity
google-github-actions/auth failed with: gitHub Actions did not inject $ACTIONS_ID_TOKEN_REQUEST_TOKEN or $ACTIONS_ID_TOKEN_REQUEST_URL into this job. This most likely means the GitHub Actions workflow permissions are incorrect, or this job is being run from a fork. For more information, please see https://docs.github.com/en/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token
Clean up images
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.