Closed renovate[bot] closed 2 months ago
Apply complete! Resources: 0 added, 0 changed, 0 destroyed.
Apply complete! Resources: 0 added, 0 changed, 0 destroyed.
Apply complete! Resources: 0 added, 0 changed, 0 destroyed.
Error: Error acquiring the state lock
Error message: workspace already locked (lock ID: "koyashiro/koyashiro-sh")
Lock Info:
ID: 2d0090eb-d5fd-9f9a-cf26-c2eaa6ccc0aa
Path:
Operation: OperationTypeApply
Who: runner@fv-az1113-548
Version: 1.8.2
Created: 2024-05-11 18:22:17.691918484 +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.
Apply complete! Resources: 0 added, 0 changed, 0 destroyed.
Apply complete! Resources: 0 added, 0 changed, 0 destroyed.
Apply complete! Resources: 0 added, 0 changed, 0 destroyed.
Apply complete! Resources: 0 added, 0 changed, 0 destroyed.
This PR contains the following updates:
v4.9.0
->v4.9.1
Release Notes
suzuki-shunsuke/tfcmt (suzuki-shunsuke/tfcmt)
### [`v4.9.1`](https://togithub.com/suzuki-shunsuke/tfcmt/releases/tag/v4.9.1) [Compare Source](https://togithub.com/suzuki-shunsuke/tfcmt/compare/v4.9.0...v4.9.1) [Pull Requests](https://togithub.com/suzuki-shunsuke/tfcmt/pulls?q=is%3Apr+milestone%3Av4.9.1) | [Issues](https://togithub.com/suzuki-shunsuke/tfcmt/issues?q=is%3Aissue+milestone%3Av4.9.1) | https://github.com/suzuki-shunsuke/tfcmt/compare/v4.9.0...v4.9.1 #### Fix [#1187](https://togithub.com/suzuki-shunsuke/tfcmt/issues/1187) [#1257](https://togithub.com/suzuki-shunsuke/tfcmt/issues/1257) [#1258](https://togithub.com/suzuki-shunsuke/tfcmt/issues/1258) Exit commands with non zero exit code if any error such as API rate limit happens This update changes the exit code of tfcmt when an error happens. The exit code was same with the exit code of `terraform plan` and `terraform apply`. This means tfcmt might have exited with zero even if tfcmt failed to post a comment due to some reason such as API rate limit. This was not a bug but a expected behavior. But this behaviour was dangerous because people might have missed unexpected changes. So this update changes the behaviour as tfcmt exits with non zero if any error such as API rate limit happens.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
â™» 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 has been generated by Mend Renovate. View repository job log here.