chore(deps-dev): bump the typescript-minor-patch group across 1 directory with 2 updates

[dependabot]

Bumps the typescript-minor-patch group with 2 updates in the /typescript directory: @langchain/core and @langchain/openai.

Updates @langchain/core from 1.1.44 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.

@​langchain/core@​1.2.0

Minor Changes

• #10924 2e28115 Thanks @​christian-bromann! - feat(core): add OpenAI-compatible stream event conversion

Patch Changes

• #11047 ac0f71d Thanks @​christian-bromann! - fix(core): preserve AIMessage content blocks

  Keep existing v1 contentBlocks when constructing AIMessage instances so serialized messages do not lose block content during deserialization.

@​langchain/core@​1.1.48

Patch Changes

• #10832 1b24369 Thanks @​info-arnav! - fix(core, openrouter): make CJS default re-exports callable

• #10666 2bb55b0 Thanks @​hnustwjj! - feat(openrouter): surface reasoning content as v1 standard content blocks

  convertOpenRouterResponseToBaseMessage and convertOpenRouterDeltaToBaseMessageChunk now copy OpenRouter's reasoning (flat string) and reasoning_details (structured array) fields onto additional_kwargs.reasoning_content / additional_kwargs.reasoning_details. A new ChatOpenRouterTranslator is registered in @langchain/core under the "openrouter" provider key so AIMessage.contentBlocks emits standard {type: "reasoning"} blocks alongside text and tool calls.

  Previously, reasoning text returned by reasoning-capable models routed through OpenRouter (DeepSeek R1, Minimax M2, Claude extended thinking, o-series, etc.) was silently dropped: only the reasoning_tokens count was preserved via usage_metadata. Consumers using standard content blocks (including the frontend agent UI patterns shown in the docs) could not display the model's chain of thought.

• #10918 3999fab Thanks @​christian-bromann! - fix(openai): stream custom tool calls through Responses API chunks

@​langchain/core@​1.1.47

Patch Changes

• #10906 f61b345 Thanks @​hntrl! - feat(core): add uuid v6 utility support

  Add v6 UUID generation support to @langchain/core/utils/uuid by vendoring the upstream uuidjs v6 implementation and its v1ToV6 helper, exporting v6 from the UUID utils index, and adding tests for deterministic generation, buffer/offset behavior, validation/versioning, and ordering.

... (truncated)

Commits

• See full diff in compare view

Updates @langchain/openai from 1.4.5 to 1.5.3

Release notes

Sourced from @​langchain/openai's releases.

@​langchain/openai@​1.5.3

Patch Changes

• #11100 3205b35 Thanks @​colifran! - fix(langchain, openai): decouple strict tools from strict structured output response

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

@​langchain/openai@​1.4.7

Patch Changes

• #10918 3999fab Thanks @​christian-bromann! - fix(openai): stream custom tool calls through Responses API chunks

• #10791 fce9ab4 Thanks @​Genmin! - fix(openai): preserve top-level Responses API ids on AI messages

@​langchain/openai@​1.4.6

Patch Changes

• #10902 229a7ad Thanks @​christian-bromann! - fix(openai): preserve v1 assistant tool calls

• #10895 36fb0ef Thanks @​BertBR! - fix(openai): guard bare JSON.parse in Responses API converter against trailing non-whitespace characters

  convertResponsesDeltaToChatGenerationChunk previously called JSON.parse(msg.text) directly when response.text.format.type === "json_schema". Some models (observed with gpt-5-mini on service_tier: "auto") intermittently emit trailing non-whitespace characters (extra tokens, control characters) after a valid JSON object, causing a SyntaxError that propagates as an unhandled exception and kills the entire streaming response mid-flight. The parse is now wrapped in a try/catch: on failure, additional_kwargs.parsed is left undefined, the stream completes normally, and the existing withStructuredOutput pipeline handles the typed failure — includeRaw: true returns { raw, parsed: null } via its withFallbacks wrapper, includeRaw: false throws a typed OutputParserException that the caller can catch and retry. Closes #10894.

Commits

• See full diff 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

[dependabot]

Labels

The following labels could not be found: area:typescript, dependencies. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.