Skip to content

build(deps): lock file maintenance (#79) #99

build(deps): lock file maintenance (#79)

build(deps): lock file maintenance (#79) #99

Triggered via push December 26, 2024 19:08
Status Failure
Total duration 29s
Artifacts

deploy.yml

on: push
deploy-gcf
20s
deploy-gcf
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 2 warnings
deploy-gcf
The v0 series of google-github-actions/setup-gcloud is no longer maintained. It will not receive updates, improvements, or security patches. Please upgrade to the latest supported versions: https://github.com/google-github-actions/setup-gcloud
deploy-gcf
google-github-actions/setup-gcloud failed with: failed to execute command `gcloud --quiet auth activate-service-account probot-google-cloud-function@***.iam.gserviceaccount.com --key-file -`: ERROR: (gcloud.auth.activate-service-account) There was a problem refreshing auth tokens for account probot-google-cloud-function@***.iam.gserviceaccount.com: ('invalid_grant: Invalid grant: account not found', ***'error': 'invalid_grant', 'error_description': 'Invalid grant: account not found'***) Please run: $ gcloud auth activate-service-account --key-file=SERVICE_ACCOUNT_FILE_PATH Or: $ gcloud auth login --cred-file=SERVICE_ACCOUNT_FILE_PATH to obtain new credentials. If you have already logged in with a different account, run: $ gcloud config set account ACCOUNT to select an already authenticated account to use.
deploy-gcf
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
deploy-gcf
"service_account_key" has been deprecated. Please switch to using google-github-actions/auth which supports both Workload Identity Federation and Service Account Key JSON authentication. For more details, see https://github.com/google-github-actions/setup-gcloud#authorization