chore(deps): bump virtualenv from 20.26.6 to 20.36.1 #13
dependabot[bot]backend.yml
on: pull_request
detect what files changed
13s
api docs test
5m 43s
backend migration tests
10m 20s
cli test
2m 11s
requirements check
30s
check migration
1m 18s
monolith-dbs test
12m 17s
backend typing
8m 28s
api url typescript generation
Matrix: backend test
Backend
2s
Annotations
25 errors and 15 warnings
|
requirements check
[@octokit/auth-app] appId option is required
|
|
backend typing
[@octokit/auth-app] appId option is required
|
|
monolith-dbs test
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.
|
|
backend test (17)
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.
|
|
backend test (16)
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.
|
|
backend test (19)
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.
|
|
backend test (15)
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.
|
|
backend test (21)
Process completed with exit code 1.
|
|
backend test (4)
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.
|
|
backend test (6)
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.
|
|
backend test (14)
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.
|
|
backend test (3)
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.
|
|
backend test (5)
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.
|
|
backend test (13)
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.
|
|
backend test (2)
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.
|
|
backend test (12)
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.
|
|
backend test (1)
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.
|
|
backend test (18)
Process completed with exit code 1.
|
|
backend test (11)
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.
|
|
backend test (8)
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.
|
|
backend test (10)
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.
|
|
backend test (20)
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.
|
|
backend test (7)
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.
|
|
backend test (0)
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.
|
|
backend test (9)
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.
|
|
requirements check
Cache not found for keys: setup-venv-Linux-py-3.13.1-/opt/hostedtoolcache/Python/3.13.1/x64/bin/python-a082b531c5e3c8ad10ae26167c430693b98d9d121a886493362c07ced86307f4-echo
|
|
check migration
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
|
check migration
Cache not found for keys: setup-venv-Linux-py-3.13.1-/opt/hostedtoolcache/Python/3.13.1/x64/bin/python-a082b531c5e3c8ad10ae26167c430693b98d9d121a886493362c07ced86307f4-cd . && uv sync --frozen --active
|
|
calculate test shards
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
|
calculate test shards
Cache not found for keys: setup-venv-Linux-py-3.13.1-/opt/hostedtoolcache/Python/3.13.1/x64/bin/python-a082b531c5e3c8ad10ae26167c430693b98d9d121a886493362c07ced86307f4-cd . && uv sync --frozen --active
|
|
cli test
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
|
cli test
Cache not found for keys: setup-venv-Linux-py-3.13.1-/opt/hostedtoolcache/Python/3.13.1/x64/bin/python-a082b531c5e3c8ad10ae26167c430693b98d9d121a886493362c07ced86307f4-cd . && uv sync --frozen --active
|
|
api docs test
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
|
api docs test
Cache not found for keys: setup-venv-Linux-py-3.13.1-/opt/hostedtoolcache/Python/3.13.1/x64/bin/python-a082b531c5e3c8ad10ae26167c430693b98d9d121a886493362c07ced86307f4-cd . && uv sync --frozen --active
|
|
backend typing
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
|
backend typing
Cache not found for keys: setup-venv-Linux-py-3.13.1-/opt/hostedtoolcache/Python/3.13.1/x64/bin/python-a082b531c5e3c8ad10ae26167c430693b98d9d121a886493362c07ced86307f4-uv sync --frozen --active
|
|
backend migration tests
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
|
backend migration tests
Cache not found for keys: setup-venv-Linux-py-3.13.1-/opt/hostedtoolcache/Python/3.13.1/x64/bin/python-a082b531c5e3c8ad10ae26167c430693b98d9d121a886493362c07ced86307f4-cd . && uv sync --frozen --active
|
|
monolith-dbs test
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
|
monolith-dbs test
Cache not found for keys: setup-venv-Linux-py-3.13.1-/opt/hostedtoolcache/Python/3.13.1/x64/bin/python-a082b531c5e3c8ad10ae26167c430693b98d9d121a886493362c07ced86307f4-cd . && uv sync --frozen --active
|