chore(deps): update dependency opentofu/opentofu to v1.10.7 #133
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:
1.9.1->1.10.7Release Notes
opentofu/opentofu (opentofu/opentofu)
v1.10.7Compare Source
SECURITY ADVISORIES:
This release contains fixes for some security advisories related to previous releases in this series.
tofu initin OpenTofu v1.10.6 and earlier could potentially use unbounded memory if there is a direct or indirect dependency on a maliciously-crafted module package distributed as a "tar" archive.This would require the attacker to coerce a root module author to depend (directly or indirectly) on a module package they control, using the HTTP, Amazon S3, or Google Cloud Storage source types to refer to a tar archive.
This release incorporates the upstream fixes for CVE-2025-58183.
When making requests to HTTPS servers, OpenTofu v1.10.6 and earlier could potentially use unbounded memory or crash with a "panic" error if TLS verification involves an excessively-long certificate chain or a chain including DSA public keys.
This affected all outgoing HTTPS requests made by OpenTofu itself, including requests to HTTPS-based state storage backends, module registries, and provider registries. For example, an attacker could coerce a root module author to depend (directly or indirectly) on a module they control which then refers to a module or provider from an attacker-controlled registry. That mode of attack would cause failures in
tofu init, at module or provider installation time.Provider plugins contain their own HTTPS client code, which may have similar problems. OpenTofu v1.10.7 cannot address similar problems within provider plugins, and so we recommend checking for similar advisories and fixes in the provider plugins you use.
This release incorporates upstream fixes for CVE-2025-58185, CVE-2025-58187, and CVE-2025-58188.
BUG FIXES:
for_eachinsidedynamicblocks can now call provider-defined functions. (#3429)Full Changelog: opentofu/opentofu@v1.10.6...v1.10.7
v1.10.6Compare Source
1.10.6
UPGRADE NOTES:
BUG FIXES:
Full Changelog: opentofu/opentofu@v1.10.5...v1.10.6
v1.10.5Compare Source
BUG FIXES:
Full Changelog: opentofu/opentofu@v1.10.4...v1.10.5
v1.10.4Compare Source
BUG FIXES:
Full Changelog: opentofu/opentofu@v1.10.3...v1.10.4
v1.10.3Compare Source
1.10.3
BUG FIXES:
tryorcanand then that expression becomes relevant for deciding whether to report a "change outside of OpenTofu" in the human-oriented plan diff. (#2988)Full Changelog: opentofu/opentofu@v1.10.2...v1.10.3
v1.10.2Compare Source
1.10.2
x-amz-server-side-encryptionheader for the lockfile. (#2870)registry.terraform.iowill no longer cause errors related to a corresponding provider onregistry.opentofu.orgwhen executing workflow commands like plan and apply. (#2979)Full Changelog: opentofu/opentofu@v1.10.1...v1.10.2
v1.10.1Compare Source
BUG FIXES:
TF_APPEND_USER_AGENThandling in the S3 remote state backend. (#2955)OTHER CHANGES:
v1.10.0Compare Source
OpenTofu 1.10.0
We're thrilled to announce the release of OpenTofu 1.10.0, our most comprehensive update yet! This release represents months of dedicated work from our community, introducing some fantastic features that will improve how OpenTofu users manage and distribute infrastructure as code.
Highlights
This release cycle introduces major new capabilities and integrations:
OCI Registry Support
Full integration with OCI registries for both provider and module distribution, valuable for organizations with private infrastructure-as-code components, air-gapped environments, or enhanced security requirements.
For more information, refer to Module Packages in OCI Registries and Provider Mirrors in OCI Registries.
Native S3 Locking
Simplify your infrastructure by using S3's conditional writes capability for state locking, eliminating the need for a separate DynamoDB table.
OpenTelemetry Tracing
Gain insights into OpenTofu operations with experimental OpenTelemetry tracing, completely local and under your control.
Resource Management with Target Files
Manage complex deployments more easily with the new
-target-fileand-exclude-fileoptions, allowing version-controlled resource targeting patterns.Compatibility Notes
ghcr.io/opentofu/opentofuimage is no longer supported as a base imageReference
v1.9.4Compare Source
1.9.4
BUG FIXES:
Full Changelog: opentofu/opentofu@v1.9.3...v1.9.4
v1.9.3Compare Source
BUG FIXES:
Full Changelog: opentofu/opentofu@v1.9.2...v1.9.3
v1.9.2Compare Source
1.9.2
BUG FIXES:
tryorcanand then that expression becomes relevant for deciding whether to report a "change outside of OpenTofu" in the human-oriented plan diff. (#2988)Full Changelog: opentofu/opentofu@v1.9.1...v1.9.2
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: 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.
This PR was generated by Mend Renovate. View the repository job log.