Add notes for agent versions (#1151)

Author: rkoron007

content/terraform-docs-agents/v1.24.x/docs/cloud-docs/agents/agent-pools.mdx

@@ -86,6 +86,12 @@ The workspace begins using the agent for Terraform runs. Runs involving an agent
 
 ## Configure Stacks to use the agent
 
+<Note>
+
+Your agents must use v1.25.0 or above to execute Stack deployment runs. To learn more about agent versioning, refer to [Updates](/terraform/cloud-docs/agents/agents#updates).
+
+</Note>
+
 Use the following steps to configure a Stack to use an agent pool.
 
 ### Step 1: Manage existing runs

content/terraform-docs-agents/v1.25.x/docs/cloud-docs/agents/agent-pools.mdx

@@ -88,6 +88,12 @@ The workspace begins using the agent for Terraform runs. Runs involving an agent
 
 ## Configure Stacks to use the agent
 
+<Note>
+
+Your agents must use v1.25.0 or above to execute Stack deployment runs. To learn more about agent versioning, refer to [Updates](/terraform/cloud-docs/agents/agents#updates).
+
+</Note>
+
 Use the following steps to configure a Stack to use an agent pool.
 
 ### Step 1: Manage existing runs

content/terraform-docs-common/docs/cloud-docs/stacks/configure.mdx

@@ -46,9 +46,15 @@ Upstream Stacks must be in the same project as their downstream Stacks. Moving a
 
 ### Change execution mode
 
-By default, HCP Terraform deploys infrastructure remotely using its own disposable virtual machines. This default execution mode is named **Remote** mode.
+By default, HCP Terraform deploys infrastructure remotely using its own disposable virtual machines. The default execution mode is called **Remote** mode. [HCP Terraform agents](/terraform/cloud-docs/agents/) let HCP Terraform communicate with isolated, private, or on-premises infrastructure.
 
-[HCP Terraform agents](/terraform/cloud-docs/agents/) let HCP Terraform communicate with isolated, private, or on-premises infrastructure. After setting up an agent and an agent pool, you can choose to change a Stack's execution mode to **Agent** to have HCP Terraform execute your Stack runs on an agent. To learn more about setting up agents, refer to [Install and run agents](/terraform/cloud-docs/agents/agents).
+<Note>
+
+Your HCP Terraform agent must use v1.25.0 or above to execute Stack deployment runs. To learn more about agent versioning, refer to [Updates](/terraform/cloud-docs/agents/agents#updates).
+
+</Note>
+
+After setting up an agent and an agent pool, you can choose to change a Stack's execution mode to **Agent** to have HCP Terraform execute your Stack runs on an agent. To learn more about setting up agents, refer to [Install and run agents](/terraform/cloud-docs/agents/agents).
 
 ## Next steps
 

content/terraform-docs-common/docs/cloud-docs/stacks/runs.mdx

@@ -15,6 +15,12 @@ HCP Terraform is designed as an execution platform for Terraform, and executes r
 
 ### Protecting private environments
 
+<Note>
+
+Your HCP Terraform agent must use v1.25.0 or above to execute Stack deployment runs. To learn more about agent versioning, refer to [Updates](/terraform/cloud-docs/agents/agents#updates).
+
+</Note>
+
 [HCP Terraform agents](/terraform/cloud-docs/agents/) let HCP Terraform communicate with isolated, private, or on-premises infrastructure. The agent polls HCP Terraform for any changes to your configuration and executes the changes locally, so you do not need to allow public ingress traffic to your resources. Agents let you control infrastructure in private environments without modifying your network perimeter. Note that [agent hooks](/terraform/cloud-docs/agents/hooks) do not support Stack workflows.
 
 ## Configuration versions