OpenTofu v1.11.12 - Provider Move Address Fixes

OpenTofu v1.11.12 was published on July 13, 2026. Its main correction makes moved blocks compare provider source addresses correctly, with a related fix ensuring that MoveResource requests receive the correct source provider address.

The full release notes and downloads are on the GitHub release page.

The first fix, tracked in PR 4280, corrects how a moved block compares provider source addresses. That address identifies the provider implementation involved in a resource move. A bad comparison at this point can make the move inconsistent with the provider configuration that OpenTofu is evaluating.

This is narrower than a general planning change. The release notes do not claim new moved block syntax, state format changes, or a new provider selection rule. They identify a comparison bug and correct it.

For data platforms, the relevant cases are infrastructure refactors around storage, compute, schedulers, and managed services. A resource address move should preserve intent in state instead of appearing as unrelated removal and creation. Teams that combine a move with a provider source change should inspect the resulting plan carefully after adopting this patch.

The second fix, tracked in PR 4355, changes the source provider address passed into provider MoveResource requests. MoveResource is the provider side hook for supported resource state moves. Supplying the right source address gives that handler the context recorded for the resource being moved.

The two fixes cover adjacent parts of the same path. OpenTofu core now compares provider source addresses correctly, then passes the correct source address when it asks the provider to process the move. Fixing only one side would leave the other boundary open to inconsistent behavior.

There is no stated performance change, provider protocol revision, or configuration migration in this release. It is a correctness patch for move handling. The release is stable, not a prerelease, and the notes contain no unrelated feature additions.

Teams that do not use moved blocks have limited direct exposure to these two bugs. Teams that move resources across provider sources or resource types have the clearest reason to prioritize v1.11.12.

Run tofu plan against a representative workspace before applying production changes. Confirm that the plan reports the intended move and does not propose unexpected removal and creation for the affected resource. Keep provider versions and input variables consistent with the earlier plan so the OpenTofu patch is the main changed variable.

Automated delivery pipelines should retain the saved plan output and provider diagnostics for comparison. If a previously failing move now succeeds, verify the destination address and resource type before apply. This patch changes correctness at a state transition boundary, where a small input error can alter the proposed action.

The notes do not provide a reproduction case or name a specific provider. That makes local plan review important, particularly when a provider implements MoveResource. Do not infer broader state repair behavior from this patch. It corrects address comparison and request input for moves that OpenTofu already supports.

For the exact commit range, the release points to the full changelog.