feat(deps): Bump @langchain/langgraph from 0.2.74 to 1.4.6

[dependabot]

Bumps @langchain/langgraph from 0.2.74 to 1.4.6.

Release notes

Sourced from @​langchain/langgraph's releases.

@​langchain/langgraph@​1.4.6

Patch Changes

• 03a0d8b Thanks @​christian-bromann! - fix(langgraph): emit valid UUIDs for exit-mode delta task_ids

  Exit-mode DeltaChannel writes used a step-prefixed synthetic task id that produced a 6-segment string Postgres rejects for checkpoint_writes.task_id uuid in LangGraph API. Embed the superstep in the first UUID group instead, matching langchain-ai/langgraph#8165.

• Updated dependencies [0558e47, 091a46f]:

  • @​langchain/langgraph-sdk@​1.9.25
  • @​langchain/langgraph-checkpoint@​1.1.3

@​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

... (truncated)

Changelog

Sourced from @​langchain/langgraph's changelog.

1.4.6

Patch Changes

• 03a0d8b Thanks @​christian-bromann! - fix(langgraph): emit valid UUIDs for exit-mode delta task_ids

  Exit-mode DeltaChannel writes used a step-prefixed synthetic task id that produced a 6-segment string Postgres rejects for checkpoint_writes.task_id uuid in LangGraph API. Embed the superstep in the first UUID group instead, matching langchain-ai/langgraph#8165.

• Updated dependencies [0558e47, 091a46f]:

  • @​langchain/langgraph-sdk@​1.9.25
  • @​langchain/langgraph-checkpoint@​1.1.3

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

... (truncated)

Commits

• 86389fa chore: version packages (#2567)
• 03a0d8b fix(langgraph): emit valid UUIDs for exit-mode delta task_ids
• 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)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​langchain/langgraph since your current version.

Install script changes

This version adds prepublish script that runs during installation. Review the package contents before updating.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)