Bump the minor-and-patch group with 4 updates

[dependabot]

Bumps the minor-and-patch group with 4 updates: @langchain/anthropic, @langchain/core, @langchain/langgraph and @xyflow/react.

Updates @langchain/anthropic from 1.5.0 to 1.5.1

Release notes

Sourced from @​langchain/anthropic's releases.

@​langchain/anthropic@​1.5.1

Patch Changes

• #11073 baa57ba Thanks @​archievi! - Stop sending thinking: { type: "disabled" } on ChatAnthropic requests when the user never configured thinking. The disabled value is now only emitted when it is explicitly set, so adaptive-only models (e.g. claude-fable-5) that reject an explicit thinking.type: "disabled" no longer fail with a 400 on a default ChatAnthropic instance.

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

Updates @langchain/core from 1.2.0 to 1.2.1

Release notes

Sourced from @​langchain/core's releases.

@​langchain/core@​1.2.1

Patch Changes

• #10674 f017708 Thanks @​christian-bromann! - fix: classify provider 429s before retrying

• #11092 7918bbd Thanks @​aolsenjazz! - fix(core): only treat arrays of content blocks as ToolMessage content

  Fix tool outputs that are arrays of plain objects being forwarded as malformed message content. An array is now only treated as message content blocks when every element is an object with a type; otherwise it is JSON-stringified.

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

Updates @langchain/langgraph from 1.4.4 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

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

Commits

• 31261c3 chore: version packages (#2558)
• 5d279df chore(deps): bump langchain (#2564)
• b1e856d feat(sdk): apply state update and goto alongside interrupt resume (#2557)
• See full diff in compare view

Updates @xyflow/react from 12.11.0 to 12.11.1

Release notes

Sourced from @​xyflow/react's releases.

@​xyflow/react@​12.11.1

Patch Changes

• #5815 87da45c - Fix FinalConnectionState type so it preserves the discriminated union.

• #5823 a6afc91 - Update attribution link

• #5824 6b1dac5 - Do not fire on pane click when connection ends on pane

• #5818 4ddc2d8 - Provide the shared handle config (connectOnClick, noPanClassName, rfId) through context instead of subscribing to the store in every Handle, so a store update no longer runs a selector once per handle

• #5817 8df250b - Reduce per-handle work on store updates by returning a shared connection state while no connection is in progress.

• #5822 a6249de - Return stable reference for edge position when connected node gets deleted

• Updated dependencies [ceb8604, 87da45c]:

  • @​xyflow/system@​0.0.78

Changelog

Sourced from @​xyflow/react's changelog.

12.11.1

Patch Changes

• #5815 87da45c - Fix FinalConnectionState type so it preserves the discriminated union.

• #5823 a6afc91 - Update attribution link

• #5824 6b1dac5 - Do not fire on pane click when connection ends on pane

• #5818 4ddc2d8 - Provide the shared handle config (connectOnClick, noPanClassName, rfId) through context instead of subscribing to the store in every Handle, so a store update no longer runs a selector once per handle

• #5817 8df250b - Reduce per-handle work on store updates by returning a shared connection state while no connection is in progress.

• #5822 a6249de - Return stable reference for edge position when connected node gets deleted

• Updated dependencies [ceb8604, 87da45c]:

  • @​xyflow/system@​0.0.78

Commits

• eedbc81 chore(packages): bump
• c7bdce4 chore(pane): cleanup
• cd5ec45 chore(react/pane): cleanup
• f919daa fix(pane): do not fire pane click when connection ends on pane
• 36c8a1a chore(attribution): update link
• 50fd4b4 Merge pull request #5823 from xyflow/refactor/attribution
• 5f1a206 chore(attr): update link
• 4710765 Merge pull request #5822 from xyflow/refactor/edge-deleted-nodes
• 503fc15 Merge branch 'main' into perf/handle-config-context
• ae1b237 refactor(edges): don't create new object when edge returns early because conn...
• Additional commits viewable in compare view

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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions