Merge pull request #311657 from AnatoliB/anatolib/orchestration-versioning-ga

Remove "public preview" notes from Orchestration Versioning docs

Author: prmerger-automator[bot]

articles/azure-functions/durable/durable-functions-orchestration-versioning.md

@@ -9,7 +9,7 @@ ms.custom: fasttrack-edit
 #Customer intent: As a Durable Functions developer, I want to deploy breaking changes to my orchestrations without interrupting in-flight instances, so that I can maintain zero-downtime deployments.
 ---
 
-# Orchestration versioning in Durable Functions (Azure Functions) - public preview
+# Orchestration versioning in Durable Functions (Azure Functions)
 
 Orchestration versioning addresses [the core challenge](durable-functions-versioning.md) of deploying changes to orchestrator functions while maintaining the deterministic execution model that Durable Functions requires. Without this feature, breaking changes to orchestrator logic or activity function signatures would cause in-flight orchestration instances to fail during replay because they would break the [determinism requirement](durable-functions-code-constraints.md) that ensures reliable orchestration execution. This built-in feature provides automatic version isolation with minimal configuration. It's backend agnostic, so it can be used by apps leveraging any of the Durable Function's [storage providers](durable-functions-storage-providers.md), including the [Durable Task Scheduler](./durable-task-scheduler/durable-task-scheduler.md).
 
@@ -36,9 +36,6 @@ The orchestration versioning feature operates on these core principles:
 
 - **Forward Protection**: The runtime automatically prevents workers running older orchestrator versions from executing orchestrations started by newer orchestrator versions.
 
-> [!IMPORTANT]
-> Orchestration versioning is currently in public preview.
-
 ## Prerequisites
 
 Before using orchestration versioning, ensure you have the required package versions for your programming language.

articles/azure-functions/durable/durable-functions-versioning.md

@@ -203,9 +203,6 @@ Because of these potential failures, the "do nothing" strategy is not recommende
 
 ### Orchestration versioning
 
-> [!NOTE]
-> Orchestration versioning is currently in public preview.
-
 The orchestration versioning feature allows different versions of orchestrations to coexist and execute concurrently without conflicts and non-determinism issues, making it possible to deploy updates while allowing in-flight orchestration instances to complete without manual intervention.
 
 With orchestration versioning:

articles/azure-functions/durable/durable-task-scheduler/durable-task-scheduler-versioning.md

@@ -1,5 +1,5 @@
 ---
-title: Configure Versioning for Durable Task Scheduler (preview)
+title: Configure Versioning for Durable Task Scheduler
 description: Learn how to use orchestration versioning in Durable Task Scheduler.
 ms.topic: how-to
 ms.date: 12/03/2025
@@ -9,7 +9,7 @@ ms.reviewer: hannahhunter
 zone_pivot_groups: df-languages
 ---
 
-# Orchestration Versioning (preview)
+# Orchestration Versioning
 
 Upgrading and downgrading orchestrations is a key consideration when working with durable orchestration systems. If an orchestration is interrupted and later resumed (for instance, during a host update), Durable Task Scheduler replays the events of the orchestration, ensuring all previous steps were executed successfully before taking the next step. This action ensures reliability, one of the core promises of the durable execution paradigm.