Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency @types/uuid to v10 #879

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 21, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/uuid (source) ^9.0.7 -> ^10.0.0 age adoption passing confidence

Review

  • Updates have been tested and work
  • If updates are AWS related, versions match the infrastructure (e.g. Lambda runtime, database, etc.)

Configuration

📅 Schedule: Branch creation - "every weekend" in timezone America/Montreal, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/uuid-10.x branch 3 times, most recently from 0880aa5 to 981a457 Compare October 25, 2024 12:30
@renovate renovate bot changed the title fix(deps): update dependency uuid to v10 chore(deps): update dependency @types/uuid to v10 Oct 27, 2024
@renovate renovate bot force-pushed the renovate/uuid-10.x branch 4 times, most recently from fc60581 to ab37b9e Compare November 6, 2024 20:45
@renovate renovate bot force-pushed the renovate/uuid-10.x branch 3 times, most recently from 19f595e to ba168ef Compare November 13, 2024 15:19
@renovate renovate bot force-pushed the renovate/uuid-10.x branch 12 times, most recently from 975e927 to a57d1ae Compare November 25, 2024 13:39
@renovate renovate bot force-pushed the renovate/uuid-10.x branch 5 times, most recently from 4e60206 to 500d523 Compare December 3, 2024 19:26
@renovate renovate bot force-pushed the renovate/uuid-10.x branch 2 times, most recently from 6ef1e15 to 09cd261 Compare January 9, 2025 19:22
@renovate renovate bot force-pushed the renovate/uuid-10.x branch 4 times, most recently from d800ef4 to e1c053e Compare January 21, 2025 14:48
@renovate renovate bot force-pushed the renovate/uuid-10.x branch 2 times, most recently from 05e8c2b to cd099a5 Compare January 29, 2025 16:02
@renovate renovate bot force-pushed the renovate/uuid-10.x branch 11 times, most recently from 8c891f5 to ada9cf8 Compare February 11, 2025 16:32
@renovate renovate bot force-pushed the renovate/uuid-10.x branch 8 times, most recently from 4335138 to ba1ecd0 Compare February 13, 2025 13:54
@renovate renovate bot force-pushed the renovate/uuid-10.x branch from ba1ecd0 to b761f87 Compare February 13, 2025 21:11
Copy link

Staging: pr_review

✅   Terraform Init: success
✅   Terraform Validate: success
✅   Terraform Format: success
❌   Terraform Plan: failed
❌   Conftest: failed

Show plan
Error: Error acquiring the state lock

Error message: operation error DynamoDB: PutItem, https response error
StatusCode: 400, RequestID:
3TM0GRN3F2MD6VT4LH5HN1L6U3VV4KQNSO5AEMVJF66Q9ASUAAJG,
ConditionalCheckFailedException: The conditional request failed
Lock Info:
  ID:        f534a765-619b-fa42-225f-89ca0fa370b8
  Path:      forms-staging-tfstate/cloud/pr_review/terraform.tfstate
  Operation: OperationTypePlan
  Who:       runner@fv-az1933-261
  Version:   1.10.5
  Created:   2025-02-13 21:13:39.051800729 +0000 UTC
  Info:      


Terraform acquires a state lock to protect the state from being written
by multiple users at the same time. Please resolve the issue above and try
again. For most commands, you can disable locking with the "-lock=false"
flag, but this is not recommended.
�[0;90m21:13:41.070�[0m �[0;31mERROR �[0m terraform invocation failed in ./.terragrunt-cache/7p-EsC9XJydLSepQWsS3iOze-tc/-syjFrdAaB-6kNXhMmF1nXBOp7o/pr_review
�[0;90m21:13:41.070�[0m �[0;31mERROR �[0m error occurred:

* Failed to execute "terraform plan -no-color -input=false -out=plan.tfplan" in ./.terragrunt-cache/7p-EsC9XJydLSepQWsS3iOze-tc/-syjFrdAaB-6kNXhMmF1nXBOp7o/pr_review
  
  Error: Error acquiring the state lock
  
  Error message: operation error DynamoDB: PutItem, https response error
  StatusCode: 400, RequestID:
  3TM0GRN3F2MD6VT4LH5HN1L6U3VV4KQNSO5AEMVJF66Q9ASUAAJG,
  ConditionalCheckFailedException: The conditional request failed
  Lock Info:
    ID:        f534a765-619b-fa42-225f-89ca0fa370b8
    Path:      forms-staging-tfstate/cloud/pr_review/terraform.tfstate
    Operation: OperationTypePlan
    Who:       runner@fv-az1933-261
    Version:   1.10.5
    Created:   2025-02-13 21:13:39.051800729 +0000 UTC
    Info:      
  
  
  Terraform acquires a state lock to protect the state from being written
  by multiple users at the same time. Please resolve the issue above and try
  again. For most commands, you can disable locking with the "-lock=false"
  flag, but this is not recommended.
  
  exit status 1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants