From 46dbb30282a8b7b357cc33a617a71173593d495e Mon Sep 17 00:00:00 2001
From: Zach Goldberg <zach@zachgoldberg.com>
Date: Mon, 13 Apr 2026 17:11:35 -0700
Subject: [PATCH 1/2] docs: add EXPERIMENT_AUTO_UNLOCK_STATE_LOCK experiment
 flag

Documents the new Pipelines experiment that automatically force-unlocks a stale
Terraform/OpenTofu state lock when an AWS session timeout causes the lock-release
step to fail mid-apply.  Currently single-unit only (no run --all support).
Default OFF.
---
 docs/2.0/reference/pipelines/feature-flags.md | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/docs/2.0/reference/pipelines/feature-flags.md b/docs/2.0/reference/pipelines/feature-flags.md
index 506535e42..571cd18f9 100644
--- a/docs/2.0/reference/pipelines/feature-flags.md
+++ b/docs/2.0/reference/pipelines/feature-flags.md
@@ -124,6 +124,21 @@ Enables Terragrunt features to reduce the potential changes during a run-all. Te
 </li>
 </ul>
 
+#### `PIPELINES_FEATURE_EXPERIMENT_AUTO_UNLOCK_STATE_LOCK`
+<ul>
+<li>
+Enables Pipelines to automatically force-unlock a stale Terraform/OpenTofu state lock when an AWS session timeout causes the lock-release step to fail mid-apply. When detected (both `Error releasing the state lock` and `ExpiredTokenException` appear in the apply output), Pipelines runs `terragrunt plan -- -lock-timeout=0s` with fresh credentials to identify the stale lock ID, then calls `terragrunt force-unlock` to release it. The original apply error is still returned — the unlock only clears the lock so the next run can proceed.
+
+Only applies to single-unit commands. Use of this feature with `run --all` is not yet supported.
+</li>
+<li>
+**Default Value**: Disabled
+</li>
+<li>
+**How to Enable**: Set to `"true"`
+</li>
+</ul>
+
 #### `PIPELINES_FEATURE_EXPERIMENT_USE_MISE_EXEC_TG_WRAPPER`
 <ul>
 <li>

From 035a5e7882a832e0207ea00705348d222fdc1060 Mon Sep 17 00:00:00 2001
From: Zach Goldberg <zach@zachgoldberg.com>
Date: Tue, 14 Apr 2026 10:35:52 -0700
Subject: [PATCH 2/2] mention tg1.0 requirement

---
 docs/2.0/reference/pipelines/feature-flags.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/docs/2.0/reference/pipelines/feature-flags.md b/docs/2.0/reference/pipelines/feature-flags.md
index 571cd18f9..d243da9ec 100644
--- a/docs/2.0/reference/pipelines/feature-flags.md
+++ b/docs/2.0/reference/pipelines/feature-flags.md
@@ -127,7 +127,9 @@ Enables Terragrunt features to reduce the potential changes during a run-all. Te
 #### `PIPELINES_FEATURE_EXPERIMENT_AUTO_UNLOCK_STATE_LOCK`
 <ul>
 <li>
-Enables Pipelines to automatically force-unlock a stale Terraform/OpenTofu state lock when an AWS session timeout causes the lock-release step to fail mid-apply. When detected (both `Error releasing the state lock` and `ExpiredTokenException` appear in the apply output), Pipelines runs `terragrunt plan -- -lock-timeout=0s` with fresh credentials to identify the stale lock ID, then calls `terragrunt force-unlock` to release it. The original apply error is still returned — the unlock only clears the lock so the next run can proceed.
+Enables Pipelines to automatically force-unlock a stale Terraform/OpenTofu state lock when an AWS session timeout causes the lock-release step to fail mid-apply. When detected (both `Error releasing the state lock` and `ExpiredTokenException` appear in the apply output), Pipelines runs `terragrunt plan -- -lock-timeout=0s` with fresh credentials to identify the stale lock ID, then calls `terragrunt force-unlock` to release it. The original apply error is still returned -- the unlock only clears the lock so the next run can proceed.
+
+Requires Terragrunt 1.0 or later. Earlier versions do not produce the structured run report that this feature depends on.
 
 Only applies to single-unit commands. Use of this feature with `run --all` is not yet supported.
 </li>