Remove "experimental" notices from update APIs (#707)

Author: dandavison

temporalio/client.py

@@ -2177,9 +2177,6 @@ async def execute_update(
         This will target the workflow with :py:attr:`run_id` if present. To use a
         different run ID, create a new handle with via :py:meth:`Client.get_workflow_handle`.
 
-        .. warning::
-           This API is experimental
-
         Args:
             update: Update function or name on the workflow.
             arg: Single argument to the update.
@@ -2284,9 +2281,6 @@ async def start_update(
         This will target the workflow with :py:attr:`run_id` if present. To use a
         different run ID, create a new handle with via :py:meth:`Client.get_workflow_handle`.
 
-        .. warning::
-           This API is experimental
-
         Args:
             update: Update function or name on the workflow. arg: Single argument to the
                 update.
@@ -2366,9 +2360,6 @@ def get_update_handle(
         Users may prefer the more typesafe :py:meth:`get_update_handle_for`
         which accepts an update definition.
 
-        .. warning::
-           This API is experimental
-
         Args:
             id: Update ID to get a handle to.
             workflow_run_id: Run ID to tie the handle to. If this is not set,
@@ -2398,9 +2389,6 @@ def get_update_handle_for(
 
         This is the same as :py:meth:`get_update_handle` but typed.
 
-        .. warning::
-           This API is experimental
-
         Args:
             update: The update method to use for typing the handle.
             id: Update ID to get a handle to.

temporalio/workflow.py

@@ -778,9 +778,6 @@ def current_update_info() -> Optional[UpdateInfo]:
     This is powered by :py:mod:`contextvars` so it is only valid within the
     update handler and coroutines/tasks it has started.
 
-    .. warning::
-       This API is experimental
-
     Returns:
         Info for the current update handler the code calling this is executing
             within if any.