Last checked and updated on 27 May 2026
How Does Terraform Handle Version Support and Lifecycle?
HashiCorp supports Generally Available (GA) releases of Terraform for up to two years.
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 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 versioning X.Y.Z.
In practice, most teams stay within the two most recent major releases to continue receiving these updates without disruption.
| Support Phase | Duration | What You Receive |
|---|---|---|
| Full Support | Within the 2-year window | Code fixes and hot fixes through minor releases on the major branch |
| Security-only | Remaining period until EOL | Critical security fixes only |
| End of Life | After 2 years | No further patches or official support |
What Risks Come With Running an Outdated Terraform Version?
Running a version past its support window means you no longer receive code fixes or hot fixes, even for issues on the major release branch.
Newer providers frequently stop compatibility testing beyond the two most recent major releases, causing terraform init or plan to fail unexpectedly.
State operations and module behaviors can also become inconsistent when the core engine falls too far behind the current supported branches.
What Actually Happens When Terraform Support Ends?
Once a Terraform major release branch reaches end of life, HashiCorp stops providing any further minor releases or patches.
Provider maintainers typically cease testing against that branch, so new provider versions may no longer work reliably with your older Terraform core.
You can continue running the binary, but you assume all responsibility for stability, security, and compatibility issues going forward.
How Do You Check Your Current Terraform Version?
Run the following command in your terminal to see the installed version:
terraform version
For JSON output including provider versions, use:
terraform version -json
Include this check early in your CI/CD pipeline to ensure you are always running a supported release.
FAQ
Q1: How many major releases back does Terraform officially support?
HashiCorp provides fixes for up to two releases from the most current major release. Staying within this window ensures you continue to receive minor version updates.
Q2: Does Terraform have traditional LTS versions?
No. Terraform uses a consistent 2-year support window per GA release rather than long-term support branches. Fixes come through minor releases on the active major branches.
Q3: What happens if I stay on a Terraform version older than the supported two major releases?
You will no longer receive code fixes or hot fixes, and newer providers may drop compatibility, leading to plan or apply failures.
Q4: How often do most teams upgrade Terraform?
Experienced teams typically upgrade every 6-12 months or when a required provider demands a newer core version.
Q5: Where can I read the official Terraform support policy?
See the HashiCorp Support Period and End-of-Life Policy for full details on how fixes are delivered across major release branches.