Skip to content

Update dependency @langchain/core to v1#738

Open
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/langchain-core-1.x
Open

Update dependency @langchain/core to v1#738
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/langchain-core-1.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Oct 18, 2025

This PR contains the following updates:

Package Change Age Confidence
@langchain/core (source) ^0.3.55^1.0.0 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

v1.1.29

Compare Source

Patch Changes
  • #​10106 9f30267 Thanks @​hntrl! - Add package version metadata to runnable traces. Each package now stamps its version in this.metadata.versions at construction time, making version info available in LangSmith trace metadata.

  • #​10154 403a99f Thanks @​kanweiwei! - fix(core): add usage_metadata to AIMessage lc_aliases

  • #​10169 3b1fd54 Thanks @​hntrl! - fix(core, langchain): bump uuid dependency from ^10.0.0 to ^11.0.0 to fix Metro bundler error

    The uuid v10 package has ambiguous exports in its package.json which causes Metro (used by Expo/React Native) to resolve the wrong entry point, resulting in Cannot read properties of undefined (reading 'v1'). The uuid v11 package fixes its exports map to work correctly with Metro's package exports resolution.

  • #​10044 77bd982 Thanks @​hntrl! - fix(core): remove inherited LangChainTracer handlers when tracingEnabled is false

    When a RunTree explicitly disables tracing via tracingEnabled: false, CallbackManager._configureSync now strips any inherited LangChainTracer handlers so child runs don't produce traces.

v1.1.28

Patch Changes

v1.1.27

Patch Changes

v1.1.26

Compare Source

Patch Changes

v1.1.25

Compare Source

Patch Changes
  • #​10002 27186c5 Thanks @​aditya-gg04! - fix(core): support reasoning/thinking blocks in StringOutputParser

  • #​10077 05396f7 Thanks @​christian-bromann! - feat(core): add ContextOverflowError, raise in anthropic and openai

  • #​10081 5a6f26b Thanks @​hntrl! - feat(core): add namespace-based symbol branding for error class hierarchies

    Introduces createNamespace utility for hierarchical symbol-based branding of class hierarchies.
    All LangChain error classes now use this pattern, replacing hand-rolled duck-type isInstance checks
    with reliable cross-realm Symbol.for-based identity.

    • New LangChainError base class that all LangChain errors extend
    • New createNamespace / Namespace API in @langchain/core/utils/namespace
    • Refactored ModelAbortError, ContextOverflowError to use namespace branding
    • Added ContextOverflowError.fromError() static factory method
    • Deprecated addLangChainErrorFields in favor of LangChainError subclasses
    • Migrated Google provider errors (GoogleError, ConfigurationError, etc.) to namespace branding
    • Updated Anthropic and OpenAI providers to use ContextOverflowError.fromError()

v1.1.24

Patch Changes

v1.1.23

Patch Changes

v1.1.22

Compare Source

Patch Changes

v1.1.21

Patch Changes

v1.1.20

Patch Changes

v1.1.19

Compare Source

Patch Changes

v1.1.18

Patch Changes
  • #​9900 a9b5059 Thanks @​hntrl! - fix(core): update method signatures to use Partial<CallOptions> for options parameters

    Updated invoke, stream, generate, and generatePrompt method signatures across Runnable, BaseChatModel, and BaseLLM to correctly accept Partial<CallOptions> instead of full CallOptions. This aligns the implementation with the RunnableInterface specification and allows users to pass partial options (e.g., { signal: abortedSignal }) without TypeScript errors.

  • #​9900 a9b5059 Thanks @​hntrl! - Improved abort signal handling for chat models:

    • Added ModelAbortError class in @langchain/core/errors that contains partial output when a model invocation is aborted mid-stream
    • invoke() now throws ModelAbortError with accumulated partialOutput when aborted during streaming (when using streaming callback handlers)
    • stream() throws a regular AbortError when aborted (since chunks are already yielded to the caller)
    • All provider implementations now properly check and propagate abort signals in both _generate() and _streamResponseChunks() methods
    • Added standard tests for abort signal behavior

v1.1.16

Compare Source

Patch Changes

v1.1.15

Patch Changes

v1.1.14

Patch Changes
  • #​9990 d5e3db0 Thanks @​hntrl! - feat(core): Add SSRF protection module (@langchain/core/utils/ssrf) with utilities for validating URLs against private IPs, cloud metadata endpoints, and localhost.

    fix(community): Harden RecursiveUrlLoader against SSRF attacks by integrating validateSafeUrl and replacing string-based URL comparison with origin-based isSameOrigin from the shared SSRF module.

  • Updated dependencies [d5e3db0, 6939dab, ad581c7]:

v1.1.13

Compare Source

Patch Changes

v1.1.12

Compare Source

Patch Changes

v1.1.11

Compare Source

Patch Changes

v1.1.10

Compare Source

Patch Changes

v1.1.9

Compare Source

Patch Changes

v1.1.8

Patch Changes

v1.1.6

Compare Source

Patch Changes

v1.1.5

Compare Source

Patch Changes

v1.1.4

Compare Source

Patch Changes

v1.1.3

Compare Source

Patch Changes

v1.1.2

Compare Source

Patch Changes

v1.1.1

Patch Changes

v1.1.0

Minor Changes
Patch Changes

v1.0.6

Patch Changes

v1.0.5

Patch Changes

v1.0.4

Patch Changes

v1.0.3

Patch Changes

v1.0.2

Patch Changes

v1.0.1

Patch Changes

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • 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.

@renovate
Copy link
Copy Markdown
Contributor Author

renovate bot commented Oct 18, 2025

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @langchain/openai@0.6.17
npm error Found: @langchain/core@1.1.39
npm error node_modules/@langchain/core
npm error   @langchain/core@"^1.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @langchain/core@">=0.3.68 <0.4.0" from @langchain/openai@0.6.17
npm error node_modules/@langchain/openai
npm error   @langchain/openai@"^0.6.0" from the root project
npm error
npm error Conflicting peer dependency: @langchain/core@0.3.80
npm error node_modules/@langchain/core
npm error   peer @langchain/core@">=0.3.68 <0.4.0" from @langchain/openai@0.6.17
npm error   node_modules/@langchain/openai
npm error     @langchain/openai@"^0.6.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-04-08T15_00_54_680Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-04-08T15_00_54_680Z-debug-0.log

@yegor256
Copy link
Copy Markdown
Member

@rultor please, try to merge, since 16 checks have passed

@rultor
Copy link
Copy Markdown
Contributor

rultor commented Oct 18, 2025

@rultor please, try to merge, since 16 checks have passed

@yegor256 OK, I'll try to merge now. You can check the progress of the merge here.

@rultor
Copy link
Copy Markdown
Contributor

rultor commented Oct 18, 2025

@rultor please, try to merge, since 16 checks have passed

@renovate[bot] @yegor256 Oops, I failed. You can see the full log here (spent 2min).

npm warn EBADENGINE }
\u001b[1G\u001b[0K⠼\u001b[1G\u001b[0K⠴\u001b[1G\u001b[0K⠦\u001b[1G\u001b[0K⠧\u001b[1G\u001b[0K⠇\u001b[1G\u001b[0K⠏\u001b[1G\u001b[0K⠋\u001b[1G\u001b[0K⠙\u001b[1G\u001b[0K⠹\u001b[1G\u001b[0K⠸\u001b[1G\u001b[0K⠼\u001b[1G\u001b[0K⠴\u001b[1G\u001b[0K⠦\u001b[1G\u001b[0K⠧\u001b[1G\u001b[0K⠇\u001b[1G\u001b[0Knpm warn deprecated rimraf@2.7.1: Rimraf versions prior to v4 are no longer supported
\u001b[1G\u001b[0K⠇\u001b[1G\u001b[0K⠏\u001b[1G\u001b[0K⠋\u001b[1G\u001b[0Knpm warn deprecated osenv@0.1.5: This package is no longer supported.
\u001b[1G\u001b[0K⠋\u001b[1G\u001b[0K⠙\u001b[1G\u001b[0K⠹\u001b[1G\u001b[0K⠸\u001b[1G\u001b[0K⠼\u001b[1G\u001b[0Knpm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
\u001b[1G\u001b[0K⠼\u001b[1G\u001b[0K⠴\u001b[1G\u001b[0Knpm warn deprecated glob@7.1.7: Glob versions prior to v9 are no longer supported
\u001b[1G\u001b[0K⠴\u001b[1G\u001b[0K⠦\u001b[1G\u001b[0K⠧\u001b[1G\u001b[0K⠇\u001b[1G\u001b[0K⠏\u001b[1G\u001b[0K⠋\u001b[1G\u001b[0K⠙\u001b[1G\u001b[0K⠹\u001b[1G\u001b[0Knpm warn deprecated glob@7.1.6: Glob versions prior to v9 are no longer supported
\u001b[1G\u001b[0K⠸\u001b[1G\u001b[0K⠼\u001b[1G\u001b[0K⠴\u001b[1G\u001b[0K⠦\u001b[1G\u001b[0K⠧\u001b[1G\u001b[0K⠇\u001b[1G\u001b[0K⠏\u001b[1G\u001b[0K⠋\u001b[1G\u001b[0K⠙\u001b[1G\u001b[0K⠹\u001b[1G\u001b[0K⠸\u001b[1G\u001b[0K⠼\u001b[1G\u001b[0K⠴\u001b[1G\u001b[0K⠦\u001b[1G\u001b[0K⠧\u001b[1G\u001b[0K⠇\u001b[1G\u001b[0K⠏\u001b[1G\u001b[0K⠋\u001b[1G\u001b[0K⠙\u001b[1G\u001b[0K⠹\u001b[1G\u001b[0K⠸\u001b[1G\u001b[0K⠼\u001b[1G\u001b[0K⠴\u001b[1G\u001b[0K⠦\u001b[1G\u001b[0K⠧\u001b[1G\u001b[0K⠇\u001b[1G\u001b[0K⠏\u001b[1G\u001b[0K⠋\u001b[1G\u001b[0K⠙\u001b[1G\u001b[0K⠹\u001b[1G\u001b[0K⠸\u001b[1G\u001b[0K⠼\u001b[1G\u001b[0K⠴\u001b[1G\u001b[0K⠦\u001b[1G\u001b[0K⠧\u001b[1G\u001b[0K⠇\u001b[1G\u001b[0K⠏\u001b[1G\u001b[0K⠋\u001b[1G\u001b[0K⠙\u001b[1G\u001b[0K⠹\u001b[1G\u001b[0K⠸\u001b[1G\u001b[0K⠼\u001b[1G\u001b[0K⠴\u001b[1G\u001b[0K⠦\u001b[1G\u001b[0K⠧\u001b[1G\u001b[0K⠇\u001b[1G\u001b[0K⠏\u001b[1G\u001b[0K⠋\u001b[1G\u001b[0K⠙\u001b[1G\u001b[0K⠹\u001b[1G\u001b[0K⠸\u001b[1G\u001b[0K⠼\u001b[1G\u001b[0K⠴\u001b[1G\u001b[0K⠦\u001b[1G\u001b[0K⠧\u001b[1G\u001b[0K⠇\u001b[1G\u001b[0K⠏\u001b[1G\u001b[0K⠋\u001b[1G\u001b[0K⠙\u001b[1G\u001b[0K⠹\u001b[1G\u001b[0K⠸\u001b[1G\u001b[0K⠼\u001b[1G\u001b[0K⠴\u001b[1G\u001b[0K⠦\u001b[1G\u001b[0K⠧\u001b[1G\u001b[0K⠇\u001b[1G\u001b[0K⠏\u001b[1G\u001b[0K⠋\u001b[1G\u001b[0K⠙\u001b[1G\u001b[0K⠹\u001b[1G\u001b[0K⠸\u001b[1G\u001b[0K⠼\u001b[1G\u001b[0K⠴\u001b[1G\u001b[0K⠦\u001b[1G\u001b[0K⠧\u001b[1G\u001b[0K⠇\u001b[1G\u001b[0K⠏\u001b[1G\u001b[0K⠋\u001b[1G\u001b[0K⠙\u001b[1G\u001b[0K⠹\u001b[1G\u001b[0K⠸\u001b[1G\u001b[0K⠼\u001b[1G\u001b[0K⠴\u001b[1G\u001b[0K⠦\u001b[1G\u001b[0K⠧\u001b[1G\u001b[0K⠇\u001b[1G\u001b[0K⠏\u001b[1G\u001b[0K⠋\u001b[1G\u001b[0K⠙\u001b[1G\u001b[0K⠹\u001b[1G\u001b[0K⠸\u001b[1G\u001b[0K⠼\u001b[1G\u001b[0K⠴\u001b[1G\u001b[0K⠦\u001b[1G\u001b[0K⠧\u001b[1G\u001b[0K
> eolang@0.0.0 postinstall
> node scripts/postinstall.js

\u001b[1G\u001b[0K⠧\u001b[1G\u001b[0KDevelopment environment detected, running patch-package...
\u001b[1mpatch-package\u001b[22m 8.0.1
Applying patches...
\u001b[1mgrunt-mocha-cli\u001b[22m@7.0.0 \u001b[32m✔\u001b[39m
\u001b[1G\u001b[0K⠙\u001b[1G\u001b[0K
added 381 packages, and audited 382 packages in 12s
\u001b[1G\u001b[0K⠙\u001b[1G\u001b[0K
\u001b[1G\u001b[0K⠙\u001b[1G\u001b[0K83 packages are looking for funding
\u001b[1G\u001b[0K⠙\u001b[1G\u001b[0K  run `npm fund` for details
\u001b[1G\u001b[0K⠙\u001b[1G\u001b[0K
4 vulnerabilities (1 moderate, 3 high)

To address all issues (including breaking changes), run:
  npm audit fix --force

Run `npm audit` for details.
\u001b[1G\u001b[0K⠙\u001b[1G\u001b[0Knpm notice
npm notice New major version of npm available! 10.8.2 -> 11.6.2
npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.6.2
npm notice To update run: npm install -g npm@11.6.2
npm notice
\u001b[1G\u001b[0K⠙\u001b[1G\u001b[0K\u001b[1G\u001b[0K⠙\u001b[1G\u001b[0K⠹\u001b[1G\u001b[0K⠸\u001b[1G\u001b[0K⠼\u001b[1G\u001b[0K⠴\u001b[1G\u001b[0K⠦\u001b[1G\u001b[0K⠧\u001b[1G\u001b[0Knpm error code ERESOLVE
\u001b[1G\u001b[0K⠧\u001b[1G\u001b[0Knpm error ERESOLVE could not resolve
\u001b[1G\u001b[0K⠧\u001b[1G\u001b[0Knpm error
\u001b[1G\u001b[0K⠧\u001b[1G\u001b[0Knpm error While resolving: @langchain/openai@0.6.16
npm error Found: @langchain/core@1.0.1
npm error node_modules/@langchain/core
npm error   @langchain/core@"^1.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @langchain/core@">=0.3.68 <0.4.0" from @langchain/openai@0.6.16
npm error node_modules/@langchain/openai
npm error   @langchain/openai@"^0.6.0" from the root project
npm error
npm error Conflicting peer dependency: @langchain/core@0.3.78
npm error node_modules/@langchain/core
npm error   peer @langchain/core@">=0.3.68 <0.4.0" from @langchain/openai@0.6.16
npm error   node_modules/@langchain/openai
npm error     @langchain/openai@"^0.6.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
\u001b[1G\u001b[0K⠧\u001b[1G\u001b[0Knpm error
npm error
npm error For a full report see:
npm error /home/r/.npm/_logs/2025-10-18T02_53_50_862Z-eresolve-report.txt
\u001b[1G\u001b[0K⠧\u001b[1G\u001b[0Knpm error A complete log of this run can be found in: /home/r/.npm/_logs/2025-10-18T02_53_50_862Z-debug-0.log
\u001b[1G\u001b[0K⠧\u001b[1G\u001b[0Kcontainer 8ab5fd9526198198bf74efca6bf9473e61964c49adb77b577381bf03f47f9597 is dead
Sat Oct 18 02:54:32 UTC 2025

@renovate renovate bot force-pushed the renovate/langchain-core-1.x branch from 66f87fd to 55cbf61 Compare October 21, 2025 11:45
@renovate renovate bot changed the title fix(deps): update dependency @langchain/core to v1 fix(deps): update dependency @langchain/core to v1 - autoclosed Oct 27, 2025
@renovate renovate bot closed this Oct 27, 2025
@renovate renovate bot deleted the renovate/langchain-core-1.x branch October 27, 2025 18:59
@renovate renovate bot changed the title fix(deps): update dependency @langchain/core to v1 - autoclosed fix(deps): update dependency @langchain/core to v1 Oct 27, 2025
@renovate renovate bot reopened this Oct 27, 2025
@renovate renovate bot force-pushed the renovate/langchain-core-1.x branch 3 times, most recently from 174613c to 200f8fe Compare October 28, 2025 03:27
@renovate renovate bot force-pushed the renovate/langchain-core-1.x branch 2 times, most recently from ce914d0 to 761ffa9 Compare November 10, 2025 16:57
@renovate renovate bot force-pushed the renovate/langchain-core-1.x branch 2 times, most recently from 0fb5bba to a9ea1f5 Compare November 18, 2025 20:08
@renovate renovate bot force-pushed the renovate/langchain-core-1.x branch from a9ea1f5 to 253ef20 Compare November 24, 2025 16:51
@renovate renovate bot force-pushed the renovate/langchain-core-1.x branch from 253ef20 to dcdf8b6 Compare December 2, 2025 04:53
@renovate renovate bot force-pushed the renovate/langchain-core-1.x branch 3 times, most recently from 7ace111 to 83ead7e Compare December 19, 2025 01:50
@renovate renovate bot force-pushed the renovate/langchain-core-1.x branch 4 times, most recently from 64012f1 to 5b016bf Compare January 7, 2026 03:23
@renovate renovate bot force-pushed the renovate/langchain-core-1.x branch from 5b016bf to 0442b48 Compare January 8, 2026 16:43
@renovate renovate bot force-pushed the renovate/langchain-core-1.x branch from 0442b48 to eca54f3 Compare January 31, 2026 01:00
@renovate renovate bot force-pushed the renovate/langchain-core-1.x branch from eca54f3 to 5aaf3d6 Compare February 17, 2026 15:54
@renovate renovate bot force-pushed the renovate/langchain-core-1.x branch 2 times, most recently from 66210b5 to b4ed86a Compare February 26, 2026 21:36
@renovate renovate bot force-pushed the renovate/langchain-core-1.x branch from b4ed86a to b40ce4d Compare March 4, 2026 01:13
@renovate renovate bot force-pushed the renovate/langchain-core-1.x branch 2 times, most recently from b260d85 to bfee8c1 Compare March 17, 2026 10:07
@renovate renovate bot changed the title fix(deps): update dependency @langchain/core to v1 Update dependency @langchain/core to v1 Mar 22, 2026
@renovate renovate bot changed the title Update dependency @langchain/core to v1 fix(deps): update dependency @langchain/core to v1 Mar 22, 2026
@renovate renovate bot force-pushed the renovate/langchain-core-1.x branch from bfee8c1 to d34c54d Compare March 24, 2026 21:24
@renovate renovate bot changed the title fix(deps): update dependency @langchain/core to v1 Update dependency @langchain/core to v1 Apr 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants