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

Update Terraform hashicorp/terraform to >= 1.5.3 #787

Merged
merged 1 commit into from
Jul 17, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 17, 2023

Mend Renovate

This PR contains the following updates:

Package Type Update Change
hashicorp/terraform required_version patch >= 1.5.2 -> >= 1.5.3

Release Notes

hashicorp/terraform (hashicorp/terraform)

v1.5.3

Compare Source

1.5.3 (July 12, 2023)

BUG FIXES:

  • core: Terraform could fail to evaluate module outputs when they are used in a provider configuration during a destroy operation (#​33462)
  • backend/consul: When failing to save state, consul CAS failed with transaction errors no longer shows an error instance memory address, but an actual error message. (#​33108)
  • plan renderer: Fixes crash when rendering the plan if a relevant attribute contains an integer index specified as a string. (#​33475)

Configuration

📅 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: Never, 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 has been generated by Mend Renovate. View repository job log here.

@pacomf pacomf merged commit 3a83f7c into main Jul 17, 2023
@pacomf pacomf deleted the renovate/hashicorp-terraform-1.x branch July 17, 2023 15:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants