v1.6.0-beta4

Bugfix time!

At the end of last week we've made a beta release changing the default provider namespace to opentofu. This had some unintended consequences on implicitly merged version requirements if you had providers referenced in both full form and short form. You can read more here.

After evaluating possible solutions to this, in order to provide the most stable experience, we've decided that the best course of action will be to roll back the change, avoid changing the default namespace, and instead deprecate the concept of short-form provider references (that skip the namespace) altogether. They will keep working, but there will be a note in the docs and in trace-level logs to encourage using the full form, namespace/provider when referencing providers.

You can find more details in the updated changelog!

You can find the whole diff here: v1.6.0-beta3...v1.6.0-beta4

v1.6.0-beta3

Important Note: the changes in this release have known issues, please avoid using it and instead use later releases.

Time for another beta release!

This release marks the last of our "renaming" changes. We're changing the default provider/module namespace in the registry to opentofu. Crucially, the old default namespace and opentofu contain the same providers in the OpenTofu registry, so this change is fully transparent. If you reference providers by name only (like random) then you will see changes to your lockfiles.

You can find more details in the updated changelog!

You can find the whole diff here: v1.6.0-beta2...v1.6.0-beta3

v1.6.0-beta2

Hey, bug fix time!

There was a bug with the new global schema cache which caused it to not be used with older versions of providers and could make execution much slower. This is now fixed.

You can find more details in the updated changelog!

You can find the whole diff here: v1.6.0-beta1...v1.6.0-beta2

v1.6.0-beta1

Hey there, important release time!

This is our first 1.6.0 beta release! This release was primarily blocked by the new registry design becoming implemented to a level where it can replace our current alpha registry. Importantly, this new registry has a slight protocol change and will require this new beta version to work for module resolving. Thus, the new registry will go live tomorrow, rather than today.

Additionally, this registry is not fully dynamic like the previous one, and contains a catalogue of providers and modules in the above repository. We've tried to include all relevant providers in modules, but if something that you're using is missing, please create an issue on the above repository, and we'll make sure to add it promptly.

Other than that we've got:

• a ton of bug fixes all over the place;
• fixes to the packaging process;
• new improved testing feature documentation that will be available tomorrow.

You can find more details in the updated changelog!

You can find the whole diff here: v1.6.0-alpha5...v1.6.0-beta1

If you have any questions, please either raise an issue on this repository, or join our Slack community!

v1.6.0-alpha5

Hey, hotfix time!

There was a bug in the S3 state backend fixes we made for alternative S3-compatible object storage systems which meant that it could fail (loudly, not silently) with server-side encryption enabled. This is now fixed.

We are also now distributing artifacts via package cloud, so installing on Linux is now much easier (thanks to BuildKite for sponsoring the PackageCloud account!).

Other than that, we have performance fixes for the testing feature and improved handling of gpg key expiry (keys that exist but have expired will for now pass with a warning, you can configure it to be strict via the OPENTOFU_ENFORCE_GPG_EXPIRATION environment variable).

You can find more details in the updated changelog!

You can find the whole diff here: v1.6.0-alpha4...v1.6.0-alpha5

v1.6.0-alpha4

Hey!

New release time!

The biggest change is the updated S3 state backend which now uses the v2 Go AWS SDK underneath. The configuration block is now more in line with the AWS provider. This includes many new config options, and associated fixes. As usual, there's also a bunch of bug fixes.

You can find more details in the updated changelog!

You can find the whole diff here: v1.6.0-alpha3...v1.6.0-alpha4

v1.6.0-alpha3

Hey!

Since the last alpha release, there's been multiple bug fixes for

• crashes caused by sensitive arguments to the import block;
• KMS key aliases not being supported;
• the new global provider schema cache not being used properly;
• the inability to disable state snapshots when the x-terraform-snapshot-interval header is absent.

Additionally, there's been many improvements to the release process, more cleanup of the code, and removals of legacy TFC/TFE mentions in stdoud-printed text. We're extremely grateful to all external contributors for their contributions!

You can find more details in the updated changelog!

Full Diff: v1.6.0-alpha2...v1.6.0-alpha3

v1.6.0-alpha2

Hey, long time no see!

Even though we've had our first alpha release just yesterday, there was an issue reported that could've negatively impacted the ability of the community to test OpenTofu with existing codebases. Thus, we've decided it was worth making a new release today, one that includes a fix to this issue.

Once again, You can find a detailed list of changes in our changelog.

Full Diff: v1.6.0-alpha1...v1.6.0-alpha2

v1.6.0-alpha1

We’re proud to publish our first alpha release!

After over a month of intense work, this release

• is a drop-in replacement, so you can take it for a spin in your existing projects - no changes required;
• uses a registry hosted by us, that will properly resolve all public providers and modules;
• is a great occasion to take tofu for a test drive and give us feedback;
• contains the 1.6 testing feature, which is engineered for feature parity with TF’s own 1.6 testing capabilities, offering a seamless transition with bug fixes and improvements (documentation still pending);
• is great to use for adapting 3rd party tooling to support OpenTofu;
• is free of checkpoint telemetry that was previously there.

It’s important to note that the registry isn’t stable yet and its availability may be spotty at times. Thus, we don’t recommend using this release for any production workflows. It’s meant to be a testing ground, first and foremost. The stable registry design process will be kicking off now, so expect more related issues to appear very soon - we’re looking forward to everybody’s feedback and participation!

We’d like to offer a special thank you to all external contributors who have created issues, discussed them, given us feedback, made code contributions, refactored parts of the codebase and/or created pull requests which are now waiting for the stable release. It’s been a humbling experience to get so much support, and we’re looking forward to continuing this journey with you!

Finally, we’d like to note that the stable release is still some time away, but you can expect more alpha releases until then.

You can find a detailed list of changes in our changelog.