build(deps): bump framer-motion from 11.3.21 to 12.11.3 #48588
dependabot[bot]Annotations
5 errors and 10 warnings
|
acceptance (4, 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.
|
|
acceptance (2, 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.
|
|
acceptance (1, 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.
|
|
acceptance (3, 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.
|
|
acceptance (0, 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.
|
|
acceptance (4, 14)
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
|
|
acceptance (4, 14)
Cache not found for keys: Linux-node-modules-8eecb3d7c24d41a82bc452bb3605ba998ecd0fce3af765e10cf7a7f179e11230
|
|
acceptance (2, 14)
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
|
|
acceptance (2, 14)
Cache not found for keys: Linux-node-modules-8eecb3d7c24d41a82bc452bb3605ba998ecd0fce3af765e10cf7a7f179e11230
|
|
acceptance (1, 14)
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
|
|
acceptance (1, 14)
Cache not found for keys: Linux-node-modules-8eecb3d7c24d41a82bc452bb3605ba998ecd0fce3af765e10cf7a7f179e11230
|
|
acceptance (3, 14)
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
|
|
acceptance (3, 14)
Cache not found for keys: Linux-node-modules-8eecb3d7c24d41a82bc452bb3605ba998ecd0fce3af765e10cf7a7f179e11230
|
|
acceptance (0, 14)
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
|
|
acceptance (0, 14)
Cache not found for keys: Linux-node-modules-8eecb3d7c24d41a82bc452bb3605ba998ecd0fce3af765e10cf7a7f179e11230
|