denis256 notes and projects

OpenTofu v1.11.11 was published on June 23, 2026 as a stable patch release for the v1.11 line. The main change is small but practical: the maintainers fixed an incomplete OTEL dependency upgrade left from the previous patch release.

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

OTEL dependency upgrade completed

This release is about finishing one dependency update, not widening behavior. The release notes say OpenTofu v1.11.11 fixes an incomplete OTEL dependencies upgrade from the previous patch release, tracked in PR #4303.

That matters because observability dependencies are part of the toolchain that many teams do not inspect until a build, scan, or runtime integration complains. In an IaC tool, OTEL support sits around telemetry and instrumentation, not around resource graph semantics. Still, incomplete dependency upgrades can create practical friction: mismatched transitive modules, scanner findings that do not line up with expectations, or package metadata that looks only partly moved.

The useful read is simple. If your team already adopted the previous v1.11 patch, v1.11.11 is the cleanup patch that makes that OTEL dependency work whole. The notes do not claim new telemetry features. They also do not mention syntax changes, provider protocol changes, or state format changes.

Why operators should still notice

Patch releases with one bug fix are easy to ignore, especially when the fix sounds internal. This one is still worth a normal toolchain bump for teams that pin OpenTofu in CI images, build their own packages, or run dependency audits against the binary build process.

The release note points at dependency completion, not end user command behavior. That makes the impact more likely to show up around packaging and compliance checks than around plan output. If your environment has SBOM checks, vulnerability policy gates, or mirror rules for approved modules, a partly completed observability dependency update can be noisy. Nobody enjoys debugging that during a release window.

This does not mean every workspace needs emergency handling. The release is not marked as a prerelease, and the notes do not describe a security issue, data loss issue, or provider compatibility change. It is a focused maintenance release. For most teams, it belongs in the next routine OpenTofu patch update.

Low behavior risk for IaC workflows

The release notes list one bug fix and no breaking change. That is useful for teams running OpenTofu in CI because small patch updates are usually taken through normal validation rather than a migration project.

For practical rollout, test the same things you already test for an OpenTofu patch: init, validate, plan, and apply in a controlled workspace. If your pipelines pin the exact OpenTofu binary version, update the pin to v1.11.11 and run the usual plan comparison. The release note gives no reason to expect plan output changes from this patch alone.

The part to watch is indirect. If your release process builds OpenTofu into base images or wraps it with internal tooling, make sure those images pick up the new tag cleanly. If you only consume official release artifacts, this is likely a simple version bump after your normal smoke test.

Scope of the patch

The concise release note is also a boundary. OpenTofu v1.11.11 is not presented as a feature release. It does not bundle a long list of CLI changes. It does not announce new language behavior. It does not describe provider install changes or registry changes.

For users, that makes the decision easier. Treat this as a maintenance update for the v1.11 stream. Teams that are staying on v1.11 should prefer the latest patch in that line after normal validation. Teams already evaluating a newer minor line should compare against their own upgrade path, but that is outside this release note.

The maintainers also link the full compare view from v1.11.10 to v1.11.11 in the release notes. Use it if your internal process requires commit level review before bumping tooling. For most operators, the GitHub release page is enough context.

Where to get it

• Release page: OpenTofu v1.11.11 release
• Repository: opentofu/opentofu
• Tag: v1.11.11