OpenTofu v1.11.2stable Released Dec 19, 2025
Impact Score: 5/10

OpenTofu v1.11.2 โ€” Release Notes & Engineering Impact

Source available โ€” automated, not human-reviewed

Component: opentofu ยท Channel: stable. Automated analysis, not a compatibility certification. How this works.

Analysis updated: 2026-11-01.

Compatibility not verified โ€” check source notes
๐Ÿ“„ .MD
โšก Executive Summary (TL;DR)

OpenTofu v1.11.2. Source highlight: The change from #2643, that was announced previously in v1.11.0, has been reverted in this release. OpenTofu will no longer directly recommend using the `-exclude=` option to work around problems caused by unknown values in provider configurations.

Who Does This Impact? (Role-Based Analysis)

๐Ÿ’ป Software Engineers & Devs

Check the source notes against the package and APIs you use before upgrading.

๐Ÿ“Š Product & Engineering Leads

Use the documented changes to assess relevance to your product; release frequency alone is not a quality measure.

โš™๏ธ DevOps & Security

Verify the target version, runtime requirements and rollback procedure in the official documentation.

๐Ÿ”ง Bug Fixes & Patches (2)

  • Fix crash in plan -generate-config-out with read-only nested attributes (#3553)
  • Fix serialization error in apply when using cloud backend (#3611)
๐Ÿ“„ View Raw Release Notes (Original Developer Log)
UPGRADE NOTES: * The change from [#2643](https://github.com/opentofu/opentofu/pull/2643), that was announced previously in v1.11.0, has been reverted in this release. OpenTofu will no longer directly recommend using the `-exclude=` option to work around problems caused by unknown values in provider configurations. Unfortunately there are existing providers that spuriously report that they cannot plan due to unknown values even when planning would have been successful, and so we cannot rely on providers to accurately signal when unknown values are the cause of an error. Using `-exclude` is still a valid workaround for these problems even though OpenTofu cannot accurately detect when it's useful to make that suggestion. BUG FIXES: * Fix crash in plan -generate-config-out with read-only nested attributes ([#3553](https://github.com/opentofu/opentofu/pull/3553)) * It's now possible again to plan changes with the `hashicorp/helm` and `hashicorp/kubernetes` providers when the provider configuration contains unknown values, as long as the configuration is carefully written to avoid the plan phase actually depending on those values. ([#3592](https://github.com/opentofu/opentofu/pull/3592)) * When running `tofu init` on Windows with an azurerm backend, the subscription_id is quoted correctly allowing successful authentication. ([#3602](https://github.com/opentofu/opentofu/pull/3602)) * Fix serialization error in apply when using cloud backend ([#3611](https://github.com/opentofu/opentofu/pull/3611)) **Full Changelog**: https://github.com/opentofu/opentofu/compare/v1.11.1...v1.11.2