You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
renovateBot
changed the title
chore(deps): update dependency @types/node to v18.11.8
chore(deps): update dependency @types/node to v18.11.9
Nov 1, 2022
renovateBot
changed the title
chore(deps): update dependency @types/node to v18.11.9
chore(deps): update dependency @types/node to v18.11.10
Nov 30, 2022
renovateBot
changed the title
chore(deps): update dependency @types/node to v18.11.10
chore(deps): update dependency @types/node to v18.11.11
Dec 5, 2022
renovateBot
changed the title
chore(deps): update dependency @types/node to v18.11.11
chore(deps): update dependency @types/node to v18.11.12
Dec 8, 2022
renovateBot
changed the title
chore(deps): update dependency @types/node to v18.11.12
chore(deps): update dependency @types/node to v18.11.13
Dec 10, 2022
renovateBot
changed the title
chore(deps): update dependency @types/node to v18.11.13
chore(deps): update dependency @types/node to v18.11.14
Dec 13, 2022
renovateBot
changed the title
chore(deps): update dependency @types/node to v18.11.14
chore(deps): update dependency @types/node to v18.11.15
Dec 13, 2022
renovateBot
changed the title
chore(deps): update dependency @types/node to v18.11.15
chore(deps): update dependency @types/node to v18.11.16
Dec 17, 2022
renovateBot
changed the title
chore(deps): update dependency @types/node to v18.11.16
Update dependency @types/node to v18.11.16
Dec 17, 2022
renovateBot
changed the title
Update dependency @types/node to v18.11.16
chore(deps): update dependency @types/node to v18.11.16
Dec 17, 2022
Running plan in Terraform Cloud. Output will stream here. Pressing Ctrl-C
will stop streaming the logs, but will not stop the plan running remotely.
Preparing the remote plan...
The remote workspace is configured to work with configuration at
infra relative to the target repository.
Terraform will upload the contents of the following directory,
excluding files or directories as defined by a .terraformignore file
at /home/runner/work/ruritoBlogger.github.io/ruritoBlogger.github.io/.terraformignore (if it is present),
in order to capture the filesystem context the remote workspace expects:
/home/runner/work/ruritoBlogger.github.io/ruritoBlogger.github.io
To view this run in a browser, visit:
https://app.terraform.io/app/rurito0125/portfolio-workspace/runs/run-2ABpDRaah1FaHhaX
Waiting for the plan to start...
Terraform v1.3.9
on linux_amd64
Initializing plugins and modules...
data.vercel_project_directory.portfolio: Reading...
data.vercel_project_directory.portfolio: Read complete after 0s [id=../frontend]
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
-/+ destroy and then create replacement
Terraform will perform the following actions:
# vercel_deployment.portfolio must be replaced
-/+ resource "vercel_deployment" "portfolio" {
~ domains = [
- "portfolio-xi-beryl-15.vercel.app",
- "portfolio-ruritoblogger.vercel.app",
] -> (known after apply) # forces replacement
~ files = { # forces replacement
~ "../frontend/package.json" = "908~2cb2f8f14d442d8c92b42a27282731ebd1e8523b" -> "909~94423efadca822b33beb9e6c2e50796b8099075a"
~ "../frontend/yarn.lock" = "75380~e5ea80ec2564a273f445181605f389e0525d6cd8" -> "75383~5eec7013fd5931b4ec4748bc2ebbd0e2ac683887"
# (72 unchanged elements hidden)
}
~ id = "dpl_Akgb4rGFgkBgYvGGesWXY9CtzP4J" -> (known after apply)
+ team_id = (known after apply) # forces replacement
~ url = "portfolio-c4utj0svk-ruritoblogger.vercel.app" -> (known after apply)
# (3 unchanged attributes hidden)
}
Plan: 1 to add, 0 to change, 1 to destroy.
Pusher: @renovate[bot], Action: pull_request, Working Directory: ``, Workflow: called terraform plan workflow
renovateBot
changed the title
Update dependency @types/node to v18.15.2
Update dependency @types/node to v18.15.3
Mar 14, 2023
Running plan in Terraform Cloud. Output will stream here. Pressing Ctrl-C
will stop streaming the logs, but will not stop the plan running remotely.
Preparing the remote plan...
The remote workspace is configured to work with configuration at
infra relative to the target repository.
Terraform will upload the contents of the following directory,
excluding files or directories as defined by a .terraformignore file
at /home/runner/work/ruritoBlogger.github.io/ruritoBlogger.github.io/.terraformignore (if it is present),
in order to capture the filesystem context the remote workspace expects:
/home/runner/work/ruritoBlogger.github.io/ruritoBlogger.github.io
To view this run in a browser, visit:
https://app.terraform.io/app/rurito0125/portfolio-workspace/runs/run-ph5xWJ2g5E6n7CMx
Waiting for the plan to start...
Terraform v1.3.9
on linux_amd64
Initializing plugins and modules...
data.vercel_project_directory.portfolio: Reading...
data.vercel_project_directory.portfolio: Read complete after 0s [id=../frontend]
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
-/+ destroy and then create replacement
Terraform will perform the following actions:
# vercel_deployment.portfolio must be replaced
-/+ resource "vercel_deployment" "portfolio" {
~ domains = [
- "portfolio-xi-beryl-15.vercel.app",
- "portfolio-ruritoblogger.vercel.app",
] -> (known after apply) # forces replacement
~ files = { # forces replacement
~ "../frontend/package.json" = "908~2cb2f8f14d442d8c92b42a27282731ebd1e8523b" -> "909~bc0643fc414fbab0cfa9077d63178951018ed667"
~ "../frontend/yarn.lock" = "75380~e5ea80ec2564a273f445181605f389e0525d6cd8" -> "75383~abe80167fab10030565ac6d6d1e86387bd440318"
# (72 unchanged elements hidden)
}
~ id = "dpl_Akgb4rGFgkBgYvGGesWXY9CtzP4J" -> (known after apply)
+ team_id = (known after apply) # forces replacement
~ url = "portfolio-c4utj0svk-ruritoblogger.vercel.app" -> (known after apply)
# (3 unchanged attributes hidden)
}
Plan: 1 to add, 0 to change, 1 to destroy.
Pusher: @renovate[bot], Action: pull_request, Working Directory: ``, Workflow: called terraform plan workflow
Running plan in Terraform Cloud. Output will stream here. Pressing Ctrl-C
will stop streaming the logs, but will not stop the plan running remotely.
Preparing the remote plan...
The remote workspace is configured to work with configuration at
infra relative to the target repository.
Terraform will upload the contents of the following directory,
excluding files or directories as defined by a .terraformignore file
at /home/runner/work/ruritoBlogger.github.io/ruritoBlogger.github.io/.terraformignore (if it is present),
in order to capture the filesystem context the remote workspace expects:
/home/runner/work/ruritoBlogger.github.io/ruritoBlogger.github.io
To view this run in a browser, visit:
https://app.terraform.io/app/rurito0125/portfolio-workspace/runs/run-Nsiii9Czqd24LJja
Waiting for the plan to start...
Terraform v1.3.9
on linux_amd64
Initializing plugins and modules...
data.vercel_project_directory.portfolio: Reading...
data.vercel_project_directory.portfolio: Read complete after 0s [id=../frontend]
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
-/+ destroy and then create replacement
Terraform will perform the following actions:
# vercel_deployment.portfolio must be replaced
-/+ resource "vercel_deployment" "portfolio" {
~ domains = [
- "portfolio-xi-beryl-15.vercel.app",
- "portfolio-ruritoblogger.vercel.app",
] -> (known after apply) # forces replacement
~ files = { # forces replacement
~ "../frontend/package.json" = "908~2cb2f8f14d442d8c92b42a27282731ebd1e8523b" -> "909~5572b1741d50a0d5ba25c8bbc7df3a76f64ce4e7"
~ "../frontend/yarn.lock" = "75380~e5ea80ec2564a273f445181605f389e0525d6cd8" -> "75383~cb029245099d021d458db36abf9ee1fce71cb14f"
# (72 unchanged elements hidden)
}
~ id = "dpl_Akgb4rGFgkBgYvGGesWXY9CtzP4J" -> (known after apply)
+ team_id = (known after apply) # forces replacement
~ url = "portfolio-c4utj0svk-ruritoblogger.vercel.app" -> (known after apply)
# (3 unchanged attributes hidden)
}
Plan: 1 to add, 0 to change, 1 to destroy.
Pusher: @renovate[bot], Action: pull_request, Working Directory: ``, Workflow: called terraform plan workflow
Running plan in Terraform Cloud. Output will stream here. Pressing Ctrl-C
will stop streaming the logs, but will not stop the plan running remotely.
Preparing the remote plan...
The remote workspace is configured to work with configuration at
infra relative to the target repository.
Terraform will upload the contents of the following directory,
excluding files or directories as defined by a .terraformignore file
at /home/runner/work/ruritoBlogger.github.io/ruritoBlogger.github.io/.terraformignore (if it is present),
in order to capture the filesystem context the remote workspace expects:
/home/runner/work/ruritoBlogger.github.io/ruritoBlogger.github.io
To view this run in a browser, visit:
https://app.terraform.io/app/rurito0125/portfolio-workspace/runs/run-Lk2YTPy6nuhgr49R
Waiting for the plan to start...
Terraform v1.3.9
on linux_amd64
Initializing plugins and modules...
data.vercel_project_directory.portfolio: Reading...
data.vercel_project_directory.portfolio: Read complete after 0s [id=../frontend]
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
-/+ destroy and then create replacement
Terraform will perform the following actions:
# vercel_deployment.portfolio must be replaced
-/+ resource "vercel_deployment" "portfolio" {
~ domains = [
- "portfolio-xi-beryl-15.vercel.app",
- "portfolio-ruritoblogger.vercel.app",
] -> (known after apply) # forces replacement
~ files = { # forces replacement
~ "../frontend/package.json" = "908~2cb2f8f14d442d8c92b42a27282731ebd1e8523b" -> "909~b98101494ef3cb3b08f4bd54dee62c8fe35b1a84"
~ "../frontend/yarn.lock" = "75380~e5ea80ec2564a273f445181605f389e0525d6cd8" -> "75383~05a1a1b9628df3efa5e670644d3a320e95983a86"
# (72 unchanged elements hidden)
}
~ id = "dpl_Akgb4rGFgkBgYvGGesWXY9CtzP4J" -> (known after apply)
+ team_id = (known after apply) # forces replacement
~ url = "portfolio-c4utj0svk-ruritoblogger.vercel.app" -> (known after apply)
# (3 unchanged attributes hidden)
}
Plan: 1 to add, 0 to change, 1 to destroy.
Pusher: @renovate[bot], Action: pull_request, Working Directory: ``, Workflow: called terraform plan workflow
Running plan in Terraform Cloud. Output will stream here. Pressing Ctrl-C
will stop streaming the logs, but will not stop the plan running remotely.
Preparing the remote plan...
The remote workspace is configured to work with configuration at
infra relative to the target repository.
Terraform will upload the contents of the following directory,
excluding files or directories as defined by a .terraformignore file
at /home/runner/work/ruritoBlogger.github.io/ruritoBlogger.github.io/.terraformignore (if it is present),
in order to capture the filesystem context the remote workspace expects:
/home/runner/work/ruritoBlogger.github.io/ruritoBlogger.github.io
To view this run in a browser, visit:
https://app.terraform.io/app/rurito0125/portfolio-workspace/runs/run-bkHMEYQwJVJV94HG
Waiting for the plan to start...
Terraform v1.3.9
on linux_amd64
Initializing plugins and modules...
data.vercel_project_directory.portfolio: Reading...
data.vercel_project_directory.portfolio: Read complete after 0s [id=../frontend]
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
-/+ destroy and then create replacement
Terraform will perform the following actions:
# vercel_deployment.portfolio must be replaced
-/+ resource "vercel_deployment" "portfolio" {
~ domains = [
- "portfolio-xi-beryl-15.vercel.app",
- "portfolio-ruritoblogger.vercel.app",
] -> (known after apply) # forces replacement
~ files = { # forces replacement
~ "../frontend/package.json" = "908~2cb2f8f14d442d8c92b42a27282731ebd1e8523b" -> "909~49ea0a73b515c019235d5fb3565d3cf939a69c04"
~ "../frontend/yarn.lock" = "75380~e5ea80ec2564a273f445181605f389e0525d6cd8" -> "75383~b29920f309bda1d0aa980cbc8d0be874f072a975"
# (72 unchanged elements hidden)
}
~ id = "dpl_Akgb4rGFgkBgYvGGesWXY9CtzP4J" -> (known after apply)
+ team_id = (known after apply) # forces replacement
~ url = "portfolio-c4utj0svk-ruritoblogger.vercel.app" -> (known after apply)
# (3 unchanged attributes hidden)
}
Plan: 1 to add, 0 to change, 1 to destroy.
Pusher: @renovate[bot], Action: pull_request, Working Directory: ``, Workflow: called terraform plan workflow
Running plan in Terraform Cloud. Output will stream here. Pressing Ctrl-C
will stop streaming the logs, but will not stop the plan running remotely.
Preparing the remote plan...
The remote workspace is configured to work with configuration at
infra relative to the target repository.
Terraform will upload the contents of the following directory,
excluding files or directories as defined by a .terraformignore file
at /home/runner/work/ruritoBlogger.github.io/ruritoBlogger.github.io/.terraformignore (if it is present),
in order to capture the filesystem context the remote workspace expects:
/home/runner/work/ruritoBlogger.github.io/ruritoBlogger.github.io
To view this run in a browser, visit:
https://app.terraform.io/app/rurito0125/portfolio-workspace/runs/run-1t59ojLRcd8ZBEhm
Waiting for the plan to start...
Terraform v1.3.9
on linux_amd64
Initializing plugins and modules...
data.vercel_project_directory.portfolio: Reading...
data.vercel_project_directory.portfolio: Read complete after 0s [id=../frontend]
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
-/+ destroy and then create replacement
Terraform will perform the following actions:
# vercel_deployment.portfolio must be replaced
-/+ resource "vercel_deployment" "portfolio" {
~ domains = [
- "portfolio-xi-beryl-15.vercel.app",
- "portfolio-ruritoblogger.vercel.app",
] -> (known after apply) # forces replacement
~ files = { # forces replacement
~ "../frontend/package.json" = "908~2cb2f8f14d442d8c92b42a27282731ebd1e8523b" -> "909~b4afeaaa327f6a42d1d1a659c6922f25e63f96a4"
~ "../frontend/yarn.lock" = "75380~e5ea80ec2564a273f445181605f389e0525d6cd8" -> "75383~385d5440f83fcffafc9ef886f242407e8afc9f8d"
# (72 unchanged elements hidden)
}
~ id = "dpl_Akgb4rGFgkBgYvGGesWXY9CtzP4J" -> (known after apply)
+ team_id = (known after apply) # forces replacement
~ url = "portfolio-c4utj0svk-ruritoblogger.vercel.app" -> (known after apply)
# (3 unchanged attributes hidden)
}
Plan: 1 to add, 0 to change, 1 to destroy.
Pusher: @renovate[bot], Action: pull_request, Working Directory: ``, Workflow: called terraform plan workflow
Running plan in Terraform Cloud. Output will stream here. Pressing Ctrl-C
will stop streaming the logs, but will not stop the plan running remotely.
Preparing the remote plan...
The remote workspace is configured to work with configuration at
infra relative to the target repository.
Terraform will upload the contents of the following directory,
excluding files or directories as defined by a .terraformignore file
at /home/runner/work/ruritoBlogger.github.io/ruritoBlogger.github.io/.terraformignore (if it is present),
in order to capture the filesystem context the remote workspace expects:
/home/runner/work/ruritoBlogger.github.io/ruritoBlogger.github.io
To view this run in a browser, visit:
https://app.terraform.io/app/rurito0125/portfolio-workspace/runs/run-sp3fLKgzF4a7Z727
Waiting for the plan to start...
Terraform v1.3.9
on linux_amd64
Initializing plugins and modules...
data.vercel_project_directory.portfolio: Reading...
data.vercel_project_directory.portfolio: Read complete after 0s [id=../frontend]
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
-/+ destroy and then create replacement
Terraform will perform the following actions:
# vercel_deployment.portfolio must be replaced
-/+ resource "vercel_deployment" "portfolio" {
~ domains = [
- "portfolio-xi-beryl-15.vercel.app",
- "portfolio-ruritoblogger.vercel.app",
] -> (known after apply) # forces replacement
~ files = { # forces replacement
~ "../frontend/package.json" = "908~2cb2f8f14d442d8c92b42a27282731ebd1e8523b" -> "909~ce02071ed6774b0cc0c291acf57a08acdd4f447b"
~ "../frontend/yarn.lock" = "75380~e5ea80ec2564a273f445181605f389e0525d6cd8" -> "75383~da3f72ea1f006f2a80c9dca79ab55296f97a4582"
# (72 unchanged elements hidden)
}
~ id = "dpl_Akgb4rGFgkBgYvGGesWXY9CtzP4J" -> (known after apply)
+ team_id = (known after apply) # forces replacement
~ url = "portfolio-c4utj0svk-ruritoblogger.vercel.app" -> (known after apply)
# (3 unchanged attributes hidden)
}
Plan: 1 to add, 0 to change, 1 to destroy.
Pusher: @renovate[bot], Action: pull_request, Working Directory: ``, Workflow: called terraform plan workflow
Running plan in Terraform Cloud. Output will stream here. Pressing Ctrl-C
will stop streaming the logs, but will not stop the plan running remotely.
Preparing the remote plan...
The remote workspace is configured to work with configuration at
infra relative to the target repository.
Terraform will upload the contents of the following directory,
excluding files or directories as defined by a .terraformignore file
at /home/runner/work/ruritoBlogger.github.io/ruritoBlogger.github.io/.terraformignore (if it is present),
in order to capture the filesystem context the remote workspace expects:
/home/runner/work/ruritoBlogger.github.io/ruritoBlogger.github.io
To view this run in a browser, visit:
https://app.terraform.io/app/rurito0125/portfolio-workspace/runs/run-smY6MraY83DEZati
Waiting for the plan to start...
Terraform v1.3.9
on linux_amd64
Initializing plugins and modules...
data.vercel_project_directory.portfolio: Reading...
data.vercel_project_directory.portfolio: Read complete after 0s [id=../frontend]
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
-/+ destroy and then create replacement
Terraform will perform the following actions:
# vercel_deployment.portfolio must be replaced
-/+ resource "vercel_deployment" "portfolio" {
~ domains = [
- "portfolio-xi-beryl-15.vercel.app",
- "portfolio-ruritoblogger.vercel.app",
] -> (known after apply) # forces replacement
~ files = { # forces replacement
~ "../frontend/package.json" = "908~2cb2f8f14d442d8c92b42a27282731ebd1e8523b" -> "910~1f189aa41dc393b3a71cf075ed5f25102a517935"
~ "../frontend/yarn.lock" = "75380~e5ea80ec2564a273f445181605f389e0525d6cd8" -> "75386~e7d0ea41af4cfe3198913f02aae261c19ec06e91"
# (72 unchanged elements hidden)
}
~ id = "dpl_Akgb4rGFgkBgYvGGesWXY9CtzP4J" -> (known after apply)
+ team_id = (known after apply) # forces replacement
~ url = "portfolio-c4utj0svk-ruritoblogger.vercel.app" -> (known after apply)
# (3 unchanged attributes hidden)
}
Plan: 1 to add, 0 to change, 1 to destroy.
Pusher: @renovate[bot], Action: pull_request, Working Directory: ``, Workflow: called terraform plan workflow
Running plan in Terraform Cloud. Output will stream here. Pressing Ctrl-C
will stop streaming the logs, but will not stop the plan running remotely.
Preparing the remote plan...
The remote workspace is configured to work with configuration at
infra relative to the target repository.
Terraform will upload the contents of the following directory,
excluding files or directories as defined by a .terraformignore file
at /home/runner/work/ruritoBlogger.github.io/ruritoBlogger.github.io/.terraformignore (if it is present),
in order to capture the filesystem context the remote workspace expects:
/home/runner/work/ruritoBlogger.github.io/ruritoBlogger.github.io
To view this run in a browser, visit:
https://app.terraform.io/app/rurito0125/portfolio-workspace/runs/run-4ZzxwJrTiNTSQS8m
Waiting for the plan to start...
Terraform v1.3.9
on linux_amd64
Initializing plugins and modules...
data.vercel_project_directory.portfolio: Reading...
data.vercel_project_directory.portfolio: Read complete after 0s [id=../frontend]
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
-/+ destroy and then create replacement
Terraform will perform the following actions:
# vercel_deployment.portfolio must be replaced
-/+ resource "vercel_deployment" "portfolio" {
~ domains = [
- "portfolio-xi-beryl-15.vercel.app",
- "portfolio-ruritoblogger.vercel.app",
] -> (known after apply) # forces replacement
~ files = { # forces replacement
~ "../frontend/package.json" = "908~2cb2f8f14d442d8c92b42a27282731ebd1e8523b" -> "910~ebf2f035f18d32d72beb0ac04905d8203652ea93"
~ "../frontend/yarn.lock" = "75380~e5ea80ec2564a273f445181605f389e0525d6cd8" -> "75386~bd81de37cabff30ce6f896b8d3c396087485f95c"
# (72 unchanged elements hidden)
}
~ id = "dpl_Akgb4rGFgkBgYvGGesWXY9CtzP4J" -> (known after apply)
+ team_id = (known after apply) # forces replacement
~ url = "portfolio-c4utj0svk-ruritoblogger.vercel.app" -> (known after apply)
# (3 unchanged attributes hidden)
}
Plan: 1 to add, 0 to change, 1 to destroy.
Pusher: @renovate[bot], Action: pull_request, Working Directory: ``, Workflow: called terraform plan workflow
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
18.0.4→18.19.130Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.