langgraph-runtime-inmem 0.32.0.dev20__tar.gz → 0.32.0.dev22__tar.gz

{langgraph_runtime_inmem-0.32.0.dev20 → langgraph_runtime_inmem-0.32.0.dev22}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: langgraph-runtime-inmem
-Version: 0.32.0.dev20
+Version: 0.32.0.dev22
 Summary: Inmem implementation for the LangGraph API server.
 Author-email: Will Fu-Hinthorn <will@langchain.dev>
 License: Elastic-2.0

{langgraph_runtime_inmem-0.32.0.dev20 → langgraph_runtime_inmem-0.32.0.dev22}/langgraph_runtime_inmem/__init__.py

@@ -10,7 +10,7 @@ from langgraph_runtime_inmem import (
     store,
 )
 
-__version__ = "0.32.0.dev20"
+__version__ = "0.32.0.dev22"
 __all__ = [
     "ops",
     "database",

{langgraph_runtime_inmem-0.32.0.dev20 → langgraph_runtime_inmem-0.32.0.dev22}/langgraph_runtime_inmem/routes.py

@@ -386,26 +386,28 @@ def get_internal_routes():
 
     async def stream_deploy_logs(request: ApiRequest):
         """SSE stream of buffered deploy events.
-
-        Each event carries a monotonic ``id``; clients can resume after a
-        disconnect by passing it back via the standard ``Last-Event-ID``
-        header (sent automatically by ``EventSource`` on auto-reconnect) or
-        a ``last_event_id`` query parameter (for explicit resume on a fresh
-        connection, since browsers don't expose a way to set the header on
-        ``new EventSource``).
-
-        Events on this stream:
-
-        * ``log`` — ``{message, level}``. ``level`` is one of ``log``, ``info``,
-          ``warn``, ``note``, ``error``, ``status_change``, ``status_url``
-          (CLI-side severity), letting the frontend color or icon lines.
-        * ``step`` — ``{event, step, message, ...}`` from the CLI.
-        * ``result`` — ``{event, status, deployment_id, message, url?, status_url?}``
-          carrying the final outcome and dashboard/app URLs without a
-          follow-up GET.
-        * ``upload_progress`` — ``{event, size_mb, pct}`` during source archive
-          upload.
-        * ``done`` / ``error`` — terminal markers with ``{exit_code}``.
+        ---
+        summary: SSE stream of buffered deploy events.
+        description: |
+            Each event carries a monotonic ``id``; clients can resume after a
+            disconnect by passing it back via the standard ``Last-Event-ID``
+            header (sent automatically by ``EventSource`` on auto-reconnect) or
+            a ``last_event_id`` query parameter (for explicit resume on a fresh
+            connection, since browsers don't expose a way to set the header on
+            ``new EventSource``).
+
+            Events on this stream:
+
+            * ``log`` — ``{message, level}``. ``level`` is one of ``log``, ``info``,
+              ``warn``, ``note``, ``error``, ``status_change``, ``status_url``
+              (CLI-side severity), letting the frontend color or icon lines.
+            * ``step`` — ``{event, step, message, ...}`` from the CLI.
+            * ``result`` — ``{event, status, deployment_id, message, url?, status_url?}``
+              carrying the final outcome and dashboard/app URLs without a
+              follow-up GET.
+            * ``upload_progress`` — ``{event, size_mb, pct}`` during source archive
+              upload.
+            * ``done`` / ``error`` — terminal markers with ``{exit_code}``.
         """
         if err := _check_deploy_origin(request):
             return err