provider-opentofu v0.2.0 bundles OpenTofu v1.8.2 instead of v1.9.0 as expected

[aashishshrestha09]

What happened?

The provider-opentofu version v0.2.0 was released with release notes stating it bundles OpenTofu runtime v1.9.0. However, after deploying the provider-opentofu:v0.2.0 package from xpkg.upbound.io and checking the embedded OpenTofu version inside the provider pod, the version remains at v1.8.2. This is inconsistent with the release notes and may cause confusion about which OpenTofu features/fixes are included.

How can we reproduce it?

1. Deploy provider-opentofu:v0.2.0 from the official registry (xpkg.upbound.io).
2. Run inside the provider pod:

   tofu version

3. Observe the version output is OpenTofu v1.8.2 instead of v1.9.0.

What environment did it happen in?

• provider-opentofu version: v0.2.0 (from xpkg.upbound.io)
• OpenTofu CLI version (local): v1.8.2
• Kubernetes version: v1.29.14
• Crossplane version: 1.17.4

[turkenf]

Thanks for noticing and reporting this @aashishshrestha09 🙏 We have a new release that fixes this issue. Please check it out.

• https://marketplace.upbound.io/providers/upbound/provider-opentofu/v0.2.6