Terraform release notes document the evolution of HashiCorp’s infrastructure-as-code tooling, from core CLI changes to Enterprise deployment packages and support timelines. The notes track stability designations, feature additions, experiments that remain alpha only, and upgrade guidance that affects existing configurations. Release frequency for the open source CLI is tracked as one week two days with 457 releases published to date, and the current star count is 48.8K. Terraform enables you to safely and predictably create, change, and improve infrastructure. It is a source-available tool that codifies APIs into declarative configuration files that can be shared amongst team members, treated as code, edited, reviewed, and versioned.
Recent Stable and Alpha Releases
The release stream for the Terraform CLI interleaves stable, release candidate, beta and alpha builds. Stability is determined by the version string and my be inaccurate. The most recent entries in the public release list include:
| Version | Stability |
|---|---|
| v1.16.0-alpha20260701 | Alpha |
| v1.16.0-alpha20260626 | Alpha |
| v1.16.0-alpha20260624 | Alpha |
| v1.15.7 | Stable |
| v1.16.0-alpha20260617 | Alpha |
| v1.15.6 | Stable |
| v1.16.0-alpha20260603 | Alpha |
| v1.15.5 | Stable |
| v1.15.4 | Stable |
| v1.16.0-alpha20260513 | Alpha |
| v1.15.3 | Stable |
| v1.15.2 | Stable |
| v1.15.1 | Stable |
| v1.15.0 | Stable |
| v1.15.0-rc4 | RC |
| v1.15.0-rc3 | RC |
| v1.14.9 | Stable |
| v1.15.0-rc2 | RC |
| v1.15.0-rc1 | RC |
| v1.15.0-beta2 | Beta |
| v1.14.8 | Stable |
| v1.15.0-beta1 | Beta |
| v1.14.7 | Stable |
| v1.15.0-alpha20260304 | Alpha |
| v1.14.6 | Stable |
The 1.16.0-alpha20260701 entry is dated July 01, 2026.
New features highlighted for v1.16.0-alpha20260701 include:
- Store PlannedPrivate data for providers
- New store block in terraform_data that can handle ephemeral and sensitive values
- Providers can now use nested blocks as computed values
- import: add support for import blocks inside modules
- We now produce builds for Linux s390x (zLinux)
- workspace: The workspace list command can now produce machine-readable output when supplied with the -json flag
- Resource action triggers can now use on_failure modes of halt, taint, or continue
Enhancements for the same build include:
- feat(cli): terraform state show accepts a -json flag
- Show info when resources are left behind due to skip_cleanup
- Action configuration now has a new caller symbol which contains the object value from the calling resource
- Actions can now use beforedestroy and afterdestroy events
- cloud: Render a summary of Terraform policy evaluation outcomes for plan and apply runs against HCP Terraform
- policy: Resolve the policy plugin entitlement (host, token, organization) from the configured cloud/remote backend for init, plan, and apply, instead of the plugin reading credentials itself
- child module outputs with unreferenced deprecated nested attributes no longer return deprecation warnings
Terraform 1.14 Feature Set
Terraform 1.14 introduces powerful new capabilities for querying existing infrastructure and executing custom provider actions beyond standard CRUD operations.
This release adds list resources, a dedicated query command, and a new actions block, along with several testing and backend improvements.
| Category | Key Changes |
|---|---|
| New Features | List Resources with *.tfquery.hcl files, terraform query command, GenerateResourceConfiguration RPC, top-level Actions block for imperative operations |
| Enhancements | Verbose test diagnostics, improved test cleanup, terraform stacks -help support, offline query validation, AWS European Sovereign Cloud support |
| Bug Fixes | Import variable handling, OSS backend proxy support, diagnostics for missing resources, unique list resource identifiers, action summary in apply, filesystem function consistency, better query error handling |
| Upgrade Notes | Possible reduced parallelism in container runtimes, macOS Monterey or later required for building |
List Resources and Query Command
Terraform 1.14 introduces list resources defined in *.tfquery.hcl files.
Terraform Enterprise Releases and Deployment
Terraform Enterprise Releases
The following table shows Terraform Enterprise releases, deployment methods, and prerequisites. Each version links to detailed release notes, which are also available in the sidebar navigation.
Below is a list of the most recent Terraform Enterprise Releases that can deploy Terraform Enterprise natively in a Kubernetes environment. Learn more about flexible deployment options.
- Refer to 2.0.x for details
- Refer to 1.2.x for details
- Refer to 1.1.x for details
- Refer to 1.0.x for details
The Enterprise release notes are organized by major line and provide deployment method specifics for Kubernetes native installs.
End-of-Life and Support Policy
Eligible code-fixes and hot-fixes are provided via a new minor release (Z) on top of the latest “major release” branch, for up to two (2) releases from the most current major release.
A major release is identified by a change in the first (X) or second (Y) digit in the following versioning nomenclature: Version X.Y.Z.
Hashicorp uses the same support period and EoL Policy for all its products. Terraform Enterprise follows a 2-year Advisory support policy.
More information is available on the Hashicorp Terraform website.
You should be running one of the supported release numbers listed above in the rightmost column.
A JSON version of this page is available at /api/v1/products/terraform/. See the API Documentation for more information. You can subscribe to the RSS feed at /terraform.atom or to the iCalendar feed at /calendar/terraform.ics.
Version identification in practice is done with:
terraform --version
Show Product Identifiers
Upgrade Notes and Experiments
Upgrade guidance is a recurring theme across release notes to avoid configuration drift.
- Provisioner bastionhostkey is now correctly applied. Existing usage of bastionhostkey should verify the configured key is correct.
Init and provider installation behavior changes are also documented:
- init: Errors due to incompatible -upgrade and -lockfile=readonly flags are now raised earlier in the init process.
- command/init: Provider installation was changed to enable future enhancements in the area. This effectively reverses the log message changes from v1.15. initializingproviderpluginmessage is being re-introduced to replace the short-lived two message types initializingproviderpluginfromconfigmessage & initializingproviderpluginfromstate_message. The change should not have any significant end-user impact aside from the command output.
- command/init: Provider installation was changed to enable future enhancements in the area. This partially reverses the init event order changes from v1.15; module installation will now occur after the backend is initialized. The change should not have any significant end-user impact aside from the command output.
Experiments are only enabled in alpha releases of Terraform CLI. The following features are not yet available in stable releases.
- The experimental "deferred actions" feature, enabled by passing the -allow-deferral option to terraform plan, permits count and for_each arguments in module, resource, and data blocks to have unknown values and allows providers to react more flexibly to unknown values.
- terraform test cleanup: The experimental test cleanup command. In experimental builds of Terraform, a manifest file and state files for each failed cleanup operation during test operations are saved within the .terraform local directory. The test cleanup command will attempt to clean up the local state files left behind automatically, without requiring manual intervention.
- terraform test: backend blocks and skipcleanup attributes:
- Test authors can now specify backend blocks within run blocks in Terraform Test files. Run blocks with backend blocks will load state from the specified backend instead of starting from empty state on every execution. This allows test authors to keep long-running test infrastructure alive between test operations, saving time during regular test operations.
- Test authors can now specify skip
Conclusion
Terraform release notes provide a continuous record of CLI evolution, Enterprise packaging, and lifecycle management. The current release cadence shows a mix of stable minor releases such as v1.15.7, v1.15.6, v1.15.5 and v1.14.9 alongside ongoing 1.16 alpha builds that preview store blocks for terraform_data, nested block computed values, import blocks inside modules, Linux s390x builds, JSON output for workspace list, and richer action trigger modes.
Terraform 1.14 remains a notable milestone for list resources expressed in *.tfquery.hcl files, the terraform query command, GenerateResourceConfiguration RPC, and a top-level Actions block for imperative operations, complemented by testing diagnostics, backend improvements, and AWS European Sovereign Cloud support.
Enterprise users must track the 2.0.x, 1.2.x, 1.1.x and 1.0.x lines for Kubernetes native deployment options, while adhering to HashiCorp’s 2-year Advisory support policy for Terraform Enterprise and the two-release Z hot-fix window on the current major branch. Upgrade notes such as corrected provisioner bastionhostkey application, earlier init error detection for -upgrade and -lockfile=readonly, and provider installation log message changes ensure safe migrations. Experiments like deferred actions and test cleanup remain alpha-only and signal future directions without stable guarantees. Collectively, the notes form the authoritative reference for version selection, compatibility planning, and feature adoption across Terraform installations.