Prepare before 1.14.4 release (#38106)

This commit is contained in:
hc-github-team-tf-core 2026-01-28 10:08:55 +00:00 committed by GitHub
parent 6435464a06
commit 3054e67ab7
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
6 changed files with 24 additions and 25 deletions

12
.changes/1.14.4.md Normal file
View file

@ -0,0 +1,12 @@
## 1.14.4 (January 28, 2026)
BUG FIXES:
* backend: Fix nil pointer dereference crash during `terraform init` when the destination backend returns an error ([#38027](https://github.com/hashicorp/terraform/issues/38027))
* Fixes an issue where any warning diagnostics generated during terraform query execution failed to render in the cloud backend session ([#38040](https://github.com/hashicorp/terraform/issues/38040))
* actions in modules without instances failed the plan graph ([#38089](https://github.com/hashicorp/terraform/issues/38089))

View file

@ -1,5 +0,0 @@
kind: BUG FIXES
body: 'backend: Fix nil pointer dereference crash during `terraform init` when the destination backend returns an error'
time: 2025-12-23T18:45:16.000000Z
custom:
Issue: "38027"

View file

@ -1,5 +0,0 @@
kind: BUG FIXES
body: Fixes an issue where any warning diagnostics generated during terraform query execution failed to render in the cloud backend session
time: 2026-01-08T11:45:27.489784-08:00
custom:
Issue: "38040"

View file

@ -1,5 +0,0 @@
kind: BUG FIXES
body: actions in modules without instances failed the plan graph
time: 2026-01-23T10:33:07.244665+01:00
custom:
Issue: "38089"

View file

@ -1,4 +1,14 @@
## 1.14.4 (Unreleased)
## 1.14.4 (January 28, 2026)
BUG FIXES:
* backend: Fix nil pointer dereference crash during `terraform init` when the destination backend returns an error ([#38027](https://github.com/hashicorp/terraform/issues/38027))
* Fixes an issue where any warning diagnostics generated during terraform query execution failed to render in the cloud backend session ([#38040](https://github.com/hashicorp/terraform/issues/38040))
* actions in modules without instances failed the plan graph ([#38089](https://github.com/hashicorp/terraform/issues/38089))
## 1.14.3 (December 17, 2025)
@ -86,15 +96,7 @@ UPGRADE NOTES:
* The parallelism of Terraform operations within container runtimes may be reduced depending on the CPU bandwidth limit setting. ([#37436](https://github.com/hashicorp/terraform/issues/37436))
* Building Terraform 1.14 requires macOS Monterey or later (due to being built on Go 1.25 which imposes these requirements) ([#37436](https://github.com/hashicorp/terraform/issues/37436))
EXPERIMENTS:
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 `skip_cleanup` 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_cleanup` attributes within test files and within run blocks. The `skip_cleanup` attribute tells `terraform test` not to clean up state files produced by run blocks with this attribute set to true. The state files for affected run blocks will be written to disk within the `.terraform` directory, where they can then be cleaned up manually using the also experimental `terraform test cleanup` command.
## Previous Releases

View file

@ -1 +1 @@
1.14.4-dev
1.14.4