LangGraph 1.2.22 was released on November 14, 2026. Its release notes describe a fix for streaming output from child graphs that run on their own thread. That is a useful boundary to examine when a nested run completes but its progress is missing from the parent's stream.
The child-stream boundary
The streaming documentation distinguishes final state from events exposed while a graph runs. Stream modes provide updates, messages, custom events and other projections. The fix concerns separate child-thread execution when the caller requests subgraph streaming.
The release also reduces several bookkeeping costs: unnecessary message conversion, broad pending-write inspection, update-key matching and repeated channel or future checks. The notes provide no quantified application speedup, so there is no measured throughput gain to report here.
A synthetic stream check
Proposed teaching experiment, not executed: create a parent graph that calls a child on a separate thread. Give the child two deterministic steps that emit distinct markers, then return a fixed value. Record the parent's stream and its final output separately. The assertions should require both child markers and the expected result. A second run with subgraph streaming disabled provides a negative control.
This separates two questions that a final-output assertion conflates: did the child finish, and did the observer receive the events it requested? Compare pinned versions under the same configuration before attributing a missing event to this fix. A successful final result alone cannot answer the observation question.
The release's license is MIT. No project implementation code is reproduced in this proposed exercise.
Sources accessed November 16, 2026. Views are my own and do not represent any employer, past or present.
Sources and evidence
Test the child event stream as well as the final result when a nested graph runs on a separate thread; this release specifically fixes that boundary.