Skip to content

Update dependency @langchain/core to v1.1.39#14106

Closed
renovate[bot] wants to merge 1 commit intomainfrom
renovate/langchain-core-1.x-lockfile
Closed

Update dependency @langchain/core to v1.1.39#14106
renovate[bot] wants to merge 1 commit intomainfrom
renovate/langchain-core-1.x-lockfile

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Apr 3, 2026

This PR contains the following updates:

Package Change Age Confidence
@langchain/core (source) 1.1.291.1.39 age confidence

Release Notes

langchain-ai/langchainjs (@​langchain/core)

v1.1.39

Compare Source

Patch Changes

v1.1.38

Compare Source

Patch Changes

v1.1.37

Compare Source

Patch Changes
  • #​10511 6933769 Thanks @​hntrl! - cache Zod-to-JSON-Schema conversions in toJsonSchema()

  • #​10541 50d5f32 Thanks @​jacoblee93! - revert: Revert "feat(core): Add all chat model/llm invocation params to metadata"

  • #​10509 5552999 Thanks @​hntrl! - feat(openai): add support for phase parameter on Responses API messages

    • Extract phase from message output items and surface it on text content blocks
    • Support phase in streaming via response.output_item.added events
    • Round-trip phase through both raw provider and standard content paths
    • Move phase into extras dict in the core standard content translator
  • #​10528 8331833 Thanks @​christian-bromann! - fix(core): normalize single-block content in mergeContent

v1.1.36

Compare Source

Patch Changes
  • #​10512 bbbfea1 Thanks @​hntrl! - fix(core): fix streaming chunk merge for providers without index on tool call deltas

    _mergeLists now falls back to id-based matching when items don't have an index field. Previously, providers routing through the OpenAI-compatible API without index on streaming tool call deltas (e.g. Anthropic models via ChatOpenAI) would accumulate hundreds of individual raw deltas in tool_call_chunks and additional_kwargs.tool_calls instead of merging them into a single entry per tool call. In a real trace with 3 concurrent subagents, this caused a single AI message to balloon from ~4KB to 146KB -- with 826 uncollapsed streaming fragments carrying a few bytes each.

    Also fixes SystemMessage.concat() which used ...this to spread all instance properties (including lc_kwargs) into the new constructor, causing each chained concat() call to nest one level deeper. After 7 middleware concat() calls (typical in deepagents), a 7KB system prompt would serialize to 81KB due to content being duplicated at every nesting level.

v1.1.35

Compare Source

Patch Changes
  • #​10327 5dc11b5 Thanks @​hntrl! - fix(core): replace exported zod type references with structural duck-type interfaces to fix TypeScript OOM

    Replaces all exported Zod type references (z3.ZodType, z4.$ZodType, etc.) in @langchain/core's public API with minimal structural ("duck-type") interfaces. This prevents TypeScript from performing expensive deep structural comparisons (~3,400+ lines of mutually recursive generics) when downstream packages resolve a different Zod version than @langchain/core, which was causing OOM crashes and unresponsive language servers in monorepo setups.

  • #​10433 7af0b65 Thanks @​tanushree-sharma! - feat: Add LangSmith integration metadata to createAgent and initChatModel

v1.1.34

Compare Source

Patch Changes

v1.1.33

Compare Source

Patch Changes

v1.1.32

Compare Source

Patch Changes
  • #​10330 26488b5 Thanks @​hntrl! - fix(core): treat empty string tool call chunk IDs as missing during merge

    Fixed _mergeLists in message base to treat empty string "" IDs the same as null/undefined when merging tool call chunks. This fixes old completions-style streaming where follow-up chunks carry id: "" instead of undefined, which previously prevented chunks from being merged by index.

  • #​10167 ca826f6 Thanks @​colifran! - feat: implement type inference for tool streams

  • #​10334 a602c42 Thanks @​maahir30! - fix(core): add JSDoc docstrings to fakeModel builder API and export FakeBuiltModel

  • #​10254 db7d017 Thanks @​pawel-twardziak! - fix(core): preserve thoughtSignature in array content during streaming with thinking models

v1.1.31

Compare Source

Patch Changes
  • #​10271 7373b4c Thanks @​jacoblee93! - feat(core): Use uuid7 instead of v4 for generating run ids

  • #​10262 b0175a5 Thanks @​maahir30! - fix: Move fakeModel from utils/testing to testing namespace
    move to updated namespace

  • #​10185 414f6ed Thanks @​maahir30! - feat: add custom Vitest matchers for LangChain message and tool call assertions

    Adds a new @langchain/core/testing/matchers export containing custom Vitest matchers (toBeHumanMessage, toBeAIMessage, toBeSystemMessage, toBeToolMessage, toHaveToolCalls, toHaveToolCallCount, toContainToolCall, toHaveToolMessages, toHaveBeenInterrupted, toHaveStructuredResponse) that external users can register via expect.extend(langchainMatchers) in their Vitest setup files. Re-exported from langchain for convenience.

v1.1.30

Compare Source

Patch Changes
  • #​10243 96c630d Thanks @​hntrl! - fix: add explicit : symbol type annotations to Symbol.for() declarations for cross-version compatibility

    TypeScript infers unique symbol type when Symbol.for() is used without an explicit type annotation, causing type incompatibility when multiple versions of the same package are present in a dependency tree. By adding explicit : symbol annotations, all declarations now use the general symbol type, making them compatible across versions while maintaining identical runtime behavior.

    Changes:

    • Added : symbol to MESSAGE_SYMBOL in messages/base.ts
    • Added : symbol to MIDDLEWARE_BRAND in agents/middleware/types.ts (also changed from Symbol() to Symbol.for() for cross-realm compatibility)
  • #​10256 a8b9ccc Thanks @​colifran! - fix(core): standard schema type guards don't support callable schemas

  • #​10204 a1f22bb Thanks @​colifran! - feat(core): implement standard schema support for structured output


Configuration

📅 Schedule: (in timezone America/Los_Angeles)

  • Branch creation
    • Between 05:00 AM and 05:59 AM, between day 1 and 7 of the month, and on Friday (* 5 1-7 * 5)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@tigent tigent bot added maintenance CI, internal documentation, automations, etc provider/community labels Apr 3, 2026
@renovate renovate bot force-pushed the renovate/langchain-core-1.x-lockfile branch from 175bb9a to 6d3d0da Compare April 4, 2026 00:29
@renovate renovate bot changed the title chore(deps): update dependency @langchain/core to v1.1.38 chore(deps): update dependency @langchain/core to v1.1.39 Apr 4, 2026
@renovate renovate bot force-pushed the renovate/langchain-core-1.x-lockfile branch from 6d3d0da to 669f191 Compare April 8, 2026 15:03
@renovate renovate bot changed the title chore(deps): update dependency @langchain/core to v1.1.39 Update dependency @langchain/core to v1.1.39 Apr 8, 2026
@renovate
Copy link
Copy Markdown
Contributor Author

renovate bot commented Apr 9, 2026

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (^1.1.5). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate renovate bot deleted the renovate/langchain-core-1.x-lockfile branch April 9, 2026 16:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

maintenance CI, internal documentation, automations, etc provider/community

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant