OpenTofu 1.13 Update Enhances Planning Capabilities
Infrastructure teams using the platform must prepare for the end of 32-bit support and new macOS requirements.
Updated on Oct. 26, 2026 in Remote Work

Live Poll
Do you feel frequent software updates provide better functionality for your projects?
OpenTofu released version 1.13 and patch 1.13.2, introducing new expression resolution capabilities while ending support for older 32-bit architectures. These updates impact infrastructure teams using the open-source configuration tool to manage automated deployment environments.
Why it matters
The updates allow module authors to resolve expressions during the planning phase, reducing uncertainty in deployment configurations. This shift helps technical operators avoid potential errors by clarifying object types and count expressions before resources are actually provisioned.
The 1.13 release represents the final series with 32-bit build support, while 1.13.2 addresses excessive CPU utilization during initial setup. Development now pivots toward stabilizing the Symbol Libraries feature in the upcoming 1.14 release.
The players
OpenTofu
An open-source infrastructure-as-code tool that provides a framework for automating cloud resource management and provisioning.
The details
Version 1.13 enables functions to resolve expressions during the planning stage, specifically allowing users to convert values to target types. This allows count expressions to resolve to zero or one by combining conversion with the assumenotnull function. Additionally, the update removes Windows Remote Management support for specific provisioners and requires macOS 13 or later, while adding support for Windows on ARM64.
Timeline
October 21, 2026: OpenTofu released the 1.13.2 patch.
August 1, 2027: Official support ends for the 1.13.x series.
Market Landscape
This release follows the project's strategy to evolve its planning engine by bridging gaps in expression handling. It marks a departure from legacy architecture support, aligning with the OpenTofu 1.14 development roadmap.
Technical leads should audit existing automation scripts to ensure they align with the new macOS and ARM64 requirements. Teams should also prepare for the eventual phase-out of the 1.13 series by August 2027 to maintain security and compatibility standards.
The takeaway
The 1.13 update provides needed predictability for infrastructure planning by allowing early expression resolution. Operators should immediately prioritize testing the new conversion functions to identify potential failures in their existing modules.
Further reading
Learn more about managing distributed engineering teams and infrastructure in the Remote Work section.
Source note: This article includes information reported by InfoQ.
Live Poll
Do you feel frequent software updates provide better functionality for your projects?





