Merge pull request #4455 from hhunter-ms/issue_3870

Workflow as stable

daprdocs/content/en/developing-applications/building-blocks/workflow/howto-author-workflow.md

@@ -6,10 +6,6 @@ weight: 5000
 description: "Learn how to develop and author workflows"
 ---
 
-{{% alert title="Note" color="primary" %}}
-Dapr Workflow is currently in beta. [See known limitations for {{% dapr-latest-version cli="true" %}}]({{< ref "workflow-overview.md#limitations" >}}).
-{{% /alert %}}
-
 This article provides a high-level overview of how to author workflows that are executed by the Dapr Workflow engine.
 
 {{% alert title="Note" color="primary" %}}

daprdocs/content/en/developing-applications/building-blocks/workflow/howto-manage-workflow.md

@@ -6,10 +6,6 @@ weight: 6000
 description: Manage and run workflows
 ---
 
-{{% alert title="Note" color="primary" %}}
-Dapr Workflow is currently in beta. [See known limitations for {{% dapr-latest-version cli="true" %}}]({{< ref "workflow-overview.md#limitations" >}}).
-{{% /alert %}}
-
 Now that you've [authored the workflow and its activities in your application]({{< ref howto-author-workflow.md >}}), you can start, terminate, and get information about the workflow using HTTP API calls. For more information, read the [workflow API reference]({{< ref workflow_api.md >}}).
 
 {{< tabs Python JavaScript ".NET" Java Go HTTP >}}

daprdocs/content/en/developing-applications/building-blocks/workflow/workflow-architecture.md

@@ -6,10 +6,6 @@ weight: 4000
 description: "The Dapr Workflow engine architecture"
 ---
 
-{{% alert title="Note" color="primary" %}}
-Dapr Workflow is currently in beta. [See known limitations for {{% dapr-latest-version cli="true" %}}]({{< ref "workflow-overview.md#limitations" >}}).
-{{% /alert %}}
-
 [Dapr Workflows]({{< ref "workflow-overview.md" >}}) allow developers to define workflows using ordinary code in a variety of programming languages. The workflow engine runs inside of the Dapr sidecar and orchestrates workflow code deployed as part of your application. This article describes:
 
 - The architecture of the Dapr Workflow engine

daprdocs/content/en/developing-applications/building-blocks/workflow/workflow-features-concepts.md

@@ -6,10 +6,6 @@ weight: 2000
 description: "Learn more about the Dapr Workflow features and concepts"
 ---
 
-{{% alert title="Note" color="primary" %}}
-Dapr Workflow is currently in beta. [See known limitations for {{% dapr-latest-version cli="true" %}}]({{< ref "workflow-overview.md#limitations" >}}).
-{{% /alert %}}
-
 Now that you've learned about the [workflow building block]({{< ref workflow-overview.md >}}) at a high level, let's deep dive into the features and concepts included with the Dapr Workflow engine and SDKs. Dapr Workflow exposes several core features and concepts which are common across all supported languages. 
 
 {{% alert title="Note" color="primary" %}}

daprdocs/content/en/developing-applications/building-blocks/workflow/workflow-overview.md

@@ -6,10 +6,6 @@ weight: 1000
 description: "Overview of Dapr Workflow"
 ---
 
-{{% alert title="Note" color="primary" %}}
-Dapr Workflow is currently in beta. [See known limitations]({{< ref "#limitations" >}}).
-{{% /alert %}}
-
 Dapr workflow makes it easy for developers to write business logic and integrations in a reliable way. Since Dapr workflows are stateful, they support long-running and fault-tolerant applications, ideal for orchestrating microservices. Dapr workflow works seamlessly with other Dapr building blocks, such as service invocation, pub/sub, state management, and bindings.
 
 The durable, resilient Dapr Workflow capability:
@@ -107,24 +103,6 @@ Want to skip the quickstarts? Not a problem. You can try out the workflow buildi
 ## Limitations
 
 - **State stores:** Due to underlying limitations in some database choices, more commonly NoSQL databases, you might run into limitations around storing internal states. For example, CosmosDB has a maximum single operation item limit of only 100 states in a single request.
-- **Horizontal scaling:** As of the 1.12.0 beta release of Dapr Workflow, it is recommended to use a maximum of two instances of Dapr per workflow application. This limitation is resolved in Dapr 1.14.x when enabling the scheduler service.
-
-To enable the scheduler service to work for Dapr Workflows, make sure you're using Dapr 1.14.x or later and assign the following configuration to your app:
-
-```yaml
-apiVersion: dapr.io/v1alpha1
-kind: Configuration
-metadata:
-  name: schedulerconfig
-spec:
-  tracing:
-    samplingRate: "1"
-  features:
-    - name: SchedulerReminders
-      enabled: true
-```
-
-See more info about [enabling preview features]({{<ref preview-features>}}).
 
 ## Watch the demo
 

daprdocs/content/en/getting-started/quickstarts/workflow-quickstart.md

@@ -6,10 +6,6 @@ weight: 73
 description: Get started with the Dapr Workflow building block
 ---
 
-{{% alert title="Note" color="primary" %}}
-Dapr Workflow is currently in beta. [See known limitations for {{% dapr-latest-version cli="true" %}}]({{< ref "workflow-overview.md#limitations" >}}).
-{{% /alert %}}
-
 {{% alert title="Note" color="primary" %}}
 Redis is currently used as the state store component for Workflows in the Quickstarts. However, Redis does not support transaction rollbacks and should not be used in production as an actor state store.
 {{% /alert %}}

daprdocs/content/en/operations/support/alpha-beta-apis.md

@@ -19,9 +19,7 @@ description: "List of current alpha and beta APIs"
 
 ## Beta APIs
 
-| Building block/API | gRPC | HTTP | Description | Documentation | Version introduced | 
-| ------------------ | ---- | ---- | ----------- | ------------- | ------------------ |
-| Workflow    |  [Workflow proto](https://github.com/dapr/dapr/blob/5aba3c9aa4ea9b3f388df125f9c66495b43c5c9e/dapr/proto/runtime/v1/dapr.proto#L151)    | `/v1.0-beta1/workflow` | The workflow API enables you to define long running, persistent processes or data flows.	 | [Workflow API]({{< ref "workflow-overview.md" >}}) | v1.10 |
+No current beta APIs.
 
 ## Related links
 

daprdocs/content/en/reference/api/workflow_api.md

@@ -6,10 +6,6 @@ description: "Detailed documentation on the workflow API"
 weight: 300
 ---
 
-{{% alert title="Note" color="primary" %}}
-Dapr Workflow is currently in beta. [See known limitations for {{% dapr-latest-version cli="true" %}}]({{< ref "workflow-overview.md#limitations" >}}).
-{{% /alert %}}
-
 Dapr provides users with the ability to interact with workflows and comes with a built-in `dapr` component.
 
 ## Start workflow request