chore(deps): bump the langgraph group across 1 directory with 2 updates

[dependabot]

Bumps the langgraph group with 2 updates in the / directory: @langchain/langgraph and @langchain/openai.

Updates @langchain/langgraph from 1.4.2 to 1.4.5

Release notes

Sourced from @​langchain/langgraph's releases.

@​langchain/langgraph@​1.4.5

Patch Changes

• #2557 b1e856d Thanks @​christian-bromann! - fix(sdk): apply state update and goto alongside interrupt resume

  respond(decision, { update, goto }) now maps to LangGraph's Command(resume, update, goto), so a human-in-the-loop UI can commit a state update (e.g. push the interrupt card into state) in the same superstep as the resume — one checkpoint, no separate updateState write, no flicker. @langchain/langgraph-api forwards update/goto through input.respond, and @langchain/core message instances in update are serialized to dicts before transport, exactly like submit(). Bumps @langchain/protocol to ^0.0.18 for the Goto type.

  respond/respondAll also apply update optimistically (mirroring submit()): the pushed messages paint immediately, with stable ids minted so the resumed run's echo reconciles them in place. Without this the interrupt is cleared the instant respond() dispatches while the pushed card only reappears a server round-trip later — so the card would flicker in that gap. The optimistic state settles on the resumed run's terminal (pending → sent, or rolled back on a failure before any echo).

  User-initiated optimistic writes (submit() / respond() / respondAll()) now commit to the store synchronously, in the same tick as the triggering event, instead of being coalesced onto the next macrotask. This lets a framework render the pushed message in the same commit as any local UI state the caller flips alongside it (e.g. a HITL form swapping its inputs for the resolved card), so the card no longer blinks out for the one-macrotask window before the flush lands. High-frequency streaming writes keep their macrotask coalescing.

• Updated dependencies [b1e856d]:

  • @​langchain/langgraph-sdk@​1.9.24

@​langchain/langgraph@​1.4.4

Patch Changes

• #2552 d662cbb Thanks @​christian-bromann! - fix(langgraph): isolate concurrent singleton-agent invocations by thread

  ensureLangGraphConfig ignores the ambient AsyncLocalStorage configurable on root-level invokes that supply an invoke-time thread_id and have no nesting keys (ignoring graph-bound .withConfig() defaults). On a fresh top-level run the ambient configurable can belong to another concurrent invocation, so its keys — internal scratchpad/task-input as well as user keys like tenant_id/user_id — must not leak in; values the caller wants arrive through the explicit (bound + invoke-time) configs. Ambient nesting (__pregel_read__) and bound child graphs invoked from parent tasks are unaffected. This prevents cross-invocation leakage between concurrent invoke() calls on a shared compiled graph (e.g. BullMQ workers with concurrency > 1). Complements the config-merge fix that stopped shared graph-bound metadata/configurable objects from being mutated across invocations

... (truncated)

Changelog

Sourced from @​langchain/langgraph's changelog.

1.4.5

Patch Changes

• #2557 b1e856d Thanks @​christian-bromann! - fix(sdk): apply state update and goto alongside interrupt resume

  respond(decision, { update, goto }) now maps to LangGraph's Command(resume, update, goto), so a human-in-the-loop UI can commit a state update (e.g. push the interrupt card into state) in the same superstep as the resume — one checkpoint, no separate updateState write, no flicker. @langchain/langgraph-api forwards update/goto through input.respond, and @langchain/core message instances in update are serialized to dicts before transport, exactly like submit(). Bumps @langchain/protocol to ^0.0.18 for the Goto type.

  respond/respondAll also apply update optimistically (mirroring submit()): the pushed messages paint immediately, with stable ids minted so the resumed run's echo reconciles them in place. Without this the interrupt is cleared the instant respond() dispatches while the pushed card only reappears a server round-trip later — so the card would flicker in that gap. The optimistic state settles on the resumed run's terminal (pending → sent, or rolled back on a failure before any echo).

  User-initiated optimistic writes (submit() / respond() / respondAll()) now commit to the store synchronously, in the same tick as the triggering event, instead of being coalesced onto the next macrotask. This lets a framework render the pushed message in the same commit as any local UI state the caller flips alongside it (e.g. a HITL form swapping its inputs for the resolved card), so the card no longer blinks out for the one-macrotask window before the flush lands. High-frequency streaming writes keep their macrotask coalescing.

• Updated dependencies [b1e856d]:

  • @​langchain/langgraph-sdk@​1.9.24

1.4.4

Patch Changes

• #2552 d662cbb Thanks @​christian-bromann! - fix(langgraph): isolate concurrent singleton-agent invocations by thread

  ensureLangGraphConfig ignores the ambient AsyncLocalStorage configurable on root-level invokes that supply an invoke-time thread_id and have no nesting keys (ignoring graph-bound .withConfig() defaults). On a fresh top-level run the ambient configurable can belong to another concurrent invocation, so its keys — internal scratchpad/task-input as well as user keys like tenant_id/user_id — must not leak in; values the caller wants arrive through the explicit (bound + invoke-time) configs. Ambient nesting (__pregel_read__) and bound child graphs invoked from parent tasks are unaffected. This prevents cross-invocation leakage between concurrent invoke() calls on a shared compiled graph (e.g. BullMQ workers with concurrency > 1). Complements the config-merge

... (truncated)

Commits

• 31261c3 chore: version packages (#2558)
• 5d279df chore(deps): bump langchain (#2564)
• b1e856d feat(sdk): apply state update and goto alongside interrupt resume (#2557)
• e6082e0 chore: version packages (#2554)
• d662cbb fix(langgraph): isolate concurrent singleton-agent invocations by thread (#2552)
• 1c2aa5b fix(langgraph): recognize JSON-erased Overwrite values across runtimes (#2553)
• 73ecaa0 chore: version packages (#2536)
• 4487214 fix(langgraph): replay concurrent DeltaChannel writes in live order (#2544)
• bc667a9 fix(langgraph): support DeltaChannel fields in StateSchema (#2549)
• e73bf8a test(langgraph-core): add test coverage on merging tags and metadata
• Additional commits viewable in compare view

Updates @langchain/openai from 1.4.7 to 1.5.2

Release notes

Sourced from @​langchain/openai's releases.

@​langchain/openai@​1.5.2

Patch Changes

• #11045 05936ab Thanks @​jackjin1997! - fix(openai): omit empty id and content on reasoning items in Responses API input

  Reasoning blocks reassembled from streaming chunks (e.g. via streamEvents) never carry an id, since OpenAI's streaming protocol only includes it in non-streaming responses. When such a message was replayed as Responses API input on the next turn, the reasoning item was emitted with id: "", which OpenAI rejects with 400 Invalid 'input[n].id': ''. The id field is now omitted when absent.

  A second error surfaced immediately after that fix: the same converter set a populated content array on the reasoning input item, which the Responses API also rejects (400 Invalid 'input[n].content': array too long. Expected an array with maximum length 0). Reasoning input items only carry summary, so content is no longer forwarded. Thanks to @​csrujanreddy for catching the second issue and verifying both fixes against the live API.

• #11065 798cb70 Thanks @​rxits! - fix(openai): route standard url file blocks to native input_file in Responses API

• #11090 80c790b Thanks @​nikhilpakhloo! - fix(openai): stream built-in tool progress events

@​langchain/openai@​1.5.1

Patch Changes

• #11001 80b43ec Thanks @​Herrtian! - Wrap Responses API stream iteration errors with existing OpenAI client error handling.

@​langchain/openai@​1.5.0

Minor Changes

• #10924 2e28115 Thanks @​christian-bromann! - feat(openai): add native streamEvents event converters

Commits

• 1ee0df0 chore: version packages (#11097)
• f017708 fix(core): better 429 error handling (#10674)
• 05936ab fix(openai): omit empty reasoning item id in Responses API input (#11045)
• 798cb70 fix(openai): route standard url file blocks to native input_file in Responses...
• 80c790b fix(openai): stream built-in tool progress events (#11090)
• d2e6afc fix(groq): require @​langchain/core >= 1.1.30 in peer dependency (#11072)
• c66870e feat(weaviate): add X-Weaviate-Client-Integration telemetry header (#11088)
• baa57ba fix(anthropic): omit default disabled thinking from requests (#11073)
• 04edb8d docs(ibm): fix "Recieved" typo in tool_choice error message (#11066)
• 2b7f368 chore(deps): bump uuid from 14.0.0 to 14.0.1 (#11094)
• Additional commits viewable in compare view