🔭 Get LangGraph alerts in real-time. Subscribe to Change Radar — Free during beta.
📡

LangGraph API Changes & Updates

We monitor LangGraph for API changes, pricing updates, model releases, deprecation notices, and service incidents.

5 Changes Detected
integration_sdk_change

langgraph-cli 0.4.21 / 0.4.20 — add validate command and remote build support for deploys

langgraph-cli 0.4.21 and 0.4.20 were published (08 Apr). The CLI gained a validate command and added remote build support for langgraph deploy flows; there are also CI/dependency bumps. These changes add new developer tooling for building and validating graph/agent deployments.

integration_sdk_change

langgraph 1.1.6 — execution info patch fix

langgraph 1.1.6 was released with a small fix to execution info patching. This is a patch release that corrects how execution information is patched at runtime and contains no API-breaking surface changes in the release notes.

integration_sdk_change

LangGraph CLI release: langgraph-cli 0.4.19 — new deploy revisions list and dependency bumps

LangGraph published a new CLI release langgraph-cli==0.4.19 (release entry shows 20 Mar 22:12). Changes include a new deploy revisions list command and several dependency bumps across CLI packages and examples.

integration_sdk_change

langgraph==1.1.2 (2026-03-12) — bugfixes and remote-graph context added

LangGraph published langgraph==1.1.2 on 2026-03-12 which includes a fix for stream part generic ordering, adds context support for the remote graph API, and bumps a dependency (tornado). The changes are primarily bug fixes and a feature addition to improve remote graph context handling.

integration_sdk_change

LangGraph 1.1.0 introduces opt-in type-safe streaming/invoke (version="v2") and migration guide

LangGraph released langgraph==1.1.0 (10 Mar 2026) adding an opt-in version="v2" streaming/invoke format that returns typed StreamPart and GraphOutput objects. The release documents how v2 yields typed dicts/objects, automatic coercion to Pydantic/dataclass schemas, and provides an explicit Migration Guide for incremental adoption. The release notes also clarify backward compatibility: v1 remains the default.