langgraph==1.2.20
Changes since 1.2.19 release(langgraph): 1.2.20 ( #9595 ) feat(langgraph): give each interrupt() in a task its own id ( #9589 ) fix(langgraph): point the multiple-interrupts error at the current docs ( #9590 ) feat(langgraph): add a strict resume mode that refuses stale interrupt answers ( #9574 ) chore(deps-dev): bump types-requests from 2.33.0.20260906 to 2.33.0.20261006 in /libs/langgraph ( #9535 ) chore(deps-dev): bump pycryptodome from 3.23.0 to 4.2.0 in /libs/langgraph in the major group (
Read original source
Source record
Research analysis
What changed
Source account: Changes since 1.2.19 release(langgraph): 1.2.20 ( #9595 ) feat(langgraph): give each interrupt() in a task its own id ( #9589 ) fix(langgraph): point the multiple-interrupts error at the current docs ( #9590 ) feat(langgraph): add a strict resume mode that refuses stale interrupt answers ( #9574 ) chore(deps-dev): bump types-requests from 2.33.0.20260906 to 2.33.0.20261006 in /libs/langgraph ( #9535 ) chore(deps-dev): bump pycryptodome from 3.23.0 to 4.2.0 in /libs/langgraph in the major group (
Version & cost evidence
A verified before/after comparison, current price units and total task cost are not attached to this record.
Who is affected
Identify the existing workflow this change affects before recommending an upgrade. Launch attention does not establish improvement; an API, pricing or availability change may instead create migration work.
Missing comparison points
Missing checks: old versus new behavior, affected plans and regions, availability date, compatibility, rollback path and cost under the same workload.
Migration check
Save the release or policy notice, run the same task on the old and new option, and compare outputs and the full bill. For retirement notices, verify the deadline before scheduling migration.