Skip to content

fix(deps): update dependency @langchain/core to v1.2.9 - #369

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

fix(deps): update dependency @langchain/core to v1.2.9#369
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/langchain-core-1.x

Conversation

@renovate

@renovate renovate Bot commented Jun 15, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

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

Release Notes

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

v1.2.9

Compare Source

Patch Changes

v1.2.8

Compare Source

Patch Changes
  • #​11369 d6ad973 Thanks @​hntrl! - fix(langchain): use unified endpoint for gateway

  • #​11342 3b0e4c4 Thanks @​thushanth-bengre-langchain! - feat(core): mark errors as retryable or not, and stop retrying the ones that aren't

    Retry middleware retried every failure up to maxRetries, including deterministic ones like a bad API key or an unknown model. Retries also nest, so a single such failure could cost dozens of API calls.

    @langchain/core/errors adds stampRetryable(error, retryable) and getRetryable(error). Marking an error leaves its class and shape untouched, so a provider SDK error can be classified without breaking instanceof. getRetryable returns undefined for errors nobody classified, and both are exported so tool authors can mark their own failures.

    modelRetryMiddleware and toolRetryMiddleware now respect the mark by default, and retries stop as soon as one is found rather than each layer spending its own budget. Aborted calls, context overflow, and oversized payloads are marked non-retryable out of the box.
    Models accept a per-call maxRetries so a surrounding retry loop can take over.

    Behavior change: errors marked non-retryable now fail on the first attempt. Unclassified errors — including any from third-party integrations or custom tools — retry exactly as before. Pass retryOn: () => true to restore the old default. A custom onFailedAttempt replaces the built-in handler and opts out of marking.

v1.2.7

Compare Source

Patch Changes

v1.2.6

Compare Source

Patch Changes
  • #​11344 f08e0c6 Thanks @​hntrl! - fix: apply [Symbol.hasInstance] method to all comparable properties using .isInstance()

    We have some internal schemas that rely on z.instanceof(). This uses a strict instanceof check which can conflict if there are multiple versions of core installed. This overrides the Symbol.hasInstance method to use the same logic as .isInstance() to compare objects at runtime.

v1.2.5

Compare Source

Patch Changes

v1.2.4

Compare Source

Patch Changes

v1.2.3

Compare Source

Patch Changes
  • #​11200 08e5888 Thanks @​hntrl! - fix(aws): normalize and safely replay Bedrock reasoning blocks

    Emit standard reasoning blocks with preserved signatures, omit incomplete signature-only reasoning during replay, and retain compatibility with legacy and redacted Bedrock reasoning.

v1.2.2

Compare Source

Patch Changes
  • #​11171 82bef01 Thanks @​christian-bromann! - fix(core): coerce string v1 AIMessage content to text blocks

    Prevent contentBlocks.push is not a function when constructing an
    AIMessage with response_metadata.output_version === "v1" and string
    content (common in serialized LangGraph stream payloads).

v1.2.1

Compare Source

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.

v1.2.0

Minor Changes

v1.1.48

Compare Source

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

v1.1.47

Compare Source

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.

  • #​10872 a640079 Thanks @​hntrl! - chore(deps): remove redundant @​types/uuid declarations

    Remove @types/uuid from package manifests that rely on @langchain/core/utils/uuid or do not require uuid type stubs directly, and refresh the lockfile entries accordingly.

  • #​10792 3682268 Thanks @​Genmin! - fix(core): apply v1 message casting after implicit streaming aggregation

  • #​10901 f26fc4a Thanks @​christian-bromann! - fix(testing): share fakeModel invocation state across bindTools instances

v1.1.46

Patch Changes
  • #​10847 1659e7d Thanks @​hntrl! - chore(core): reduce transitive dependency exposure and tighten release hygiene

    Remove direct runtime dependencies on ansi-styles, camelcase, and decamelize
    by inlining equivalent logic in core internals, and enable npm provenance in the
    release workflow.

  • #​10790 ef78bc6 Thanks @​Genmin! - fix(core): keep different content block types separate when merging chunks


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 renovate Bot changed the title fix(deps): update dependency @langchain/core to v1.1.49 fix(deps): update dependency @langchain/core to v1.2.0 Jun 17, 2026
@renovate
renovate Bot force-pushed the renovate/langchain-core-1.x branch 3 times, most recently from 0f4c495 to b460e93 Compare June 22, 2026 18:02
@renovate renovate Bot changed the title fix(deps): update dependency @langchain/core to v1.2.0 fix(deps): update dependency @langchain/core to v1.2.1 Jun 22, 2026
@renovate
renovate Bot force-pushed the renovate/langchain-core-1.x branch from b460e93 to 5c348ee Compare July 9, 2026 10:52
@renovate renovate Bot changed the title fix(deps): update dependency @langchain/core to v1.2.1 fix(deps): update dependency @langchain/core to v1.2.2 Jul 9, 2026
@renovate
renovate Bot force-pushed the renovate/langchain-core-1.x branch 2 times, most recently from 1fb5153 to b7c4df5 Compare July 14, 2026 23:06
@renovate renovate Bot changed the title fix(deps): update dependency @langchain/core to v1.2.2 fix(deps): update dependency @langchain/core to v1.2.3 Jul 14, 2026
@renovate
renovate Bot force-pushed the renovate/langchain-core-1.x branch 2 times, most recently from 271b947 to 5e74057 Compare July 24, 2026 15:07
@renovate
renovate Bot force-pushed the renovate/langchain-core-1.x branch 2 times, most recently from fd372e4 to 024dbba Compare July 30, 2026 23:03
@renovate renovate Bot changed the title fix(deps): update dependency @langchain/core to v1.2.3 fix(deps): update dependency @langchain/core to v1.2.4 Jul 30, 2026
@renovate
renovate Bot force-pushed the renovate/langchain-core-1.x branch from 024dbba to 6a1e19e Compare August 6, 2026 00:51
@renovate renovate Bot changed the title fix(deps): update dependency @langchain/core to v1.2.4 fix(deps): update dependency @langchain/core to v1.2.5 Aug 6, 2026
@renovate
renovate Bot force-pushed the renovate/langchain-core-1.x branch 2 times, most recently from 0627fc6 to 945623c Compare August 12, 2026 21:41
@renovate renovate Bot changed the title fix(deps): update dependency @langchain/core to v1.2.5 fix(deps): update dependency @langchain/core to v1.2.6 Aug 12, 2026
@renovate
renovate Bot force-pushed the renovate/langchain-core-1.x branch from 945623c to b47ad3b Compare August 13, 2026 22:52
@renovate renovate Bot changed the title fix(deps): update dependency @langchain/core to v1.2.6 fix(deps): update dependency @langchain/core to v1.2.7 Aug 13, 2026
@renovate
renovate Bot force-pushed the renovate/langchain-core-1.x branch from b47ad3b to 9cea600 Compare August 14, 2026 22:46
@renovate renovate Bot changed the title fix(deps): update dependency @langchain/core to v1.2.7 fix(deps): update dependency @langchain/core to v1.2.8 Aug 14, 2026
@renovate
renovate Bot force-pushed the renovate/langchain-core-1.x branch from 9cea600 to 3fff732 Compare August 20, 2026 02:10
@renovate renovate Bot changed the title fix(deps): update dependency @langchain/core to v1.2.8 fix(deps): update dependency @langchain/core to v1.2.9 Aug 20, 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.

0 participants