Skip to content

chore: version packages - #2

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main
Open

github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Mar 12, 2026

Copy link
Copy Markdown

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@langchain/langgraph-sdk@1.11.0

Minor Changes

  • #2831 3234c69 Thanks @ramon-langchain! - Expose connection lifecycle callbacks for built-in streaming transports.

    onConnected runs after the initial SSE or WebSocket connection becomes usable and after every successful reconnect. Its payload distinguishes an initial connection from a reconnected connection and includes the reconnect attempt number.

    onReconnect now also receives the scheduled delayMs, allowing applications to display accurate retry state before the next connection attempt. React, Vue, Svelte, and Angular stream hooks forward both callbacks.

Patch Changes

  • #2831 3234c69 Thanks @ramon-langchain! - Recover cleanly when a thread's root event stream terminates unexpectedly.

    If the stream fails or closes while a run is active, the controller now records the transport error and clears isLoading rather than leaving the UI in a permanently running state. Once the failed pump settles, a later submission can start a fresh root subscription without recreating the thread stream or replaying the failed command.

  • #2809 11a4535 Thanks @hntrl! - fix(sdk): appropriately track persisted seq for stream replay

    Sequences weren't being appropriately attributed when rehydrating the page (e.g. on refresh). This meant we'd lose stream information on useStream on reloads. This has been fixed by adding a lookup step to determine what the most appropriate sequence index is to track in the event stream.:x

  • #2762 2fab6fd Thanks @JessYanCoding! - Send checkpoint_id in the runs.stream() request body, so a checkpointId passed to client.runs.stream() forks from the requested checkpoint instead of being silently dropped. Matches runs.create() and runs.wait(), which already send it.

  • #2813 4fc118f Thanks @eliornl! - fix(sdk): show interrupts raised after a passive thread rejoin

    After a page refresh mid-run, useStream filtered every interrupt it did not
    already know from the hydrated thread state as replayed history, and waited
    for a checkpoints event to lift that filter. Current runtimes never emit
    that event and the replay buffer trims it on long runs, so interrupts raised
    after the refresh never appeared until the next reload. Unknown interrupts are
    now settled against the server's thread state when the run reaches a terminal
    lifecycle: the ones the server lists as pending are shown, the rest are
    dropped as history.

  • #2812 db4bdad Thanks @eliornl! - fix(sdk): recover from a server-side thread stream drop instead of freezing

    The protocol SSE transport now reconnects when the server closes the event
    stream cleanly. The thread stream is open-ended, so a clean close only happens
    when the server's own upstream consumer died or it is restarting; before, the
    client treated it as the end of the thread and the UI froze mid-run with no
    error. A connection that delivered events also resets the reconnect budget, so
    long-lived pages survive repeated deploys. maxReconnectAttempts: 0 keeps the
    old end-on-close behavior.

    Unsolicited server error frames (no command id) and a shared stream that gives
    up reconnecting now reach stream.error: ThreadStream.onError exposes them,
    useStream sets error, clears isLoading, and settles the in-flight
    submit() as failed.

  • #2808 55fa26b Thanks @hntrl! - fix(sdk): coalesce locally resolved interrupts

    when resolving interrupts using useStream, there was a case where we prioritized the remote state values (which we lookup in React Strict mode on every page transition) over the local interrupt responses we know we've responded with.

    This has since been fixed to first prioritize the local cache of interrupts, resolved against the remote state values when a run hits a terminal event

@langchain/angular@1.1.0

Minor Changes

  • #2831 3234c69 Thanks @ramon-langchain! - Expose connection lifecycle callbacks for built-in streaming transports.

    onConnected runs after the initial SSE or WebSocket connection becomes usable and after every successful reconnect. Its payload distinguishes an initial connection from a reconnected connection and includes the reconnect attempt number.

    onReconnect now also receives the scheduled delayMs, allowing applications to display accurate retry state before the next connection attempt. React, Vue, Svelte, and Angular stream hooks forward both callbacks.

Patch Changes

@langchain/react@1.1.0

Minor Changes

  • #2831 3234c69 Thanks @ramon-langchain! - Expose connection lifecycle callbacks for built-in streaming transports.

    onConnected runs after the initial SSE or WebSocket connection becomes usable and after every successful reconnect. Its payload distinguishes an initial connection from a reconnected connection and includes the reconnect attempt number.

    onReconnect now also receives the scheduled delayMs, allowing applications to display accurate retry state before the next connection attempt. React, Vue, Svelte, and Angular stream hooks forward both callbacks.

Patch Changes

@langchain/svelte@1.1.0

Minor Changes

  • #2831 3234c69 Thanks @ramon-langchain! - Expose connection lifecycle callbacks for built-in streaming transports.

    onConnected runs after the initial SSE or WebSocket connection becomes usable and after every successful reconnect. Its payload distinguishes an initial connection from a reconnected connection and includes the reconnect attempt number.

    onReconnect now also receives the scheduled delayMs, allowing applications to display accurate retry state before the next connection attempt. React, Vue, Svelte, and Angular stream hooks forward both callbacks.

Patch Changes

@langchain/vue@1.1.0

Minor Changes

  • #2831 3234c69 Thanks @ramon-langchain! - Expose connection lifecycle callbacks for built-in streaming transports.

    onConnected runs after the initial SSE or WebSocket connection becomes usable and after every successful reconnect. Its payload distinguishes an initial connection from a reconnected connection and includes the reconnect attempt number.

    onReconnect now also receives the scheduled delayMs, allowing applications to display accurate retry state before the next connection attempt. React, Vue, Svelte, and Angular stream hooks forward both callbacks.

Patch Changes

@langchain/langgraph-api@1.4.6

Patch Changes

  • #2751 0a9611a Thanks @t3s7r! - fix(api): run.start with input on a cancelled thread no longer folds the input into Command(resume). A cancelled run shares the "interrupted" status with a genuine interrupt() pause, but has no pending interrupt to consume the resume value, so the submitted message was silently dropped. The input-vs-resume decision now keys on whether the thread actually has pending interrupts (both in the protocol service and the embed protocol).
  • Updated dependencies []:
    • @langchain/langgraph-ui@1.4.6

@langchain/langgraph-cli@1.4.6

Patch Changes

  • Updated dependencies [0a9611a]:
    • @langchain/langgraph-api@1.4.6

@langchain/langgraph@1.4.15

Patch Changes

  • #2794 83a4b62 Thanks @hntrl! - feat(langgraph): add per-node tracePolicy input/output processors and omitPayload

    Transform the payloads recorded on a node's own trace run while retaining its span and timing. Processors receive raw values and fall back to the original payload if they throw. Graph state, root runs, and child runs remain unchanged when processors do not mutate their arguments.

    Matches Python's callback-level behavior: transforms also affect chain events and message streaming, so omitting outputs can suppress messages returned directly by nodes and omitting inputs can affect message deduplication.

  • Updated dependencies [3234c69, 3234c69, 11a4535, 2fab6fd, 4fc118f, db4bdad, 55fa26b]:

    • @langchain/langgraph-sdk@1.11.0

@langchain/langgraph-cua@1.0.3

No changes in this release.

@langchain/langgraph-supervisor@1.1.2

No changes in this release.

@langchain/langgraph-swarm@1.0.3

No changes in this release.

@langchain/langgraph-ui@1.4.6

No changes in this release.

@github-actions
github-actions Bot force-pushed the changeset-release/main branch 5 times, most recently from e055d6b to 3221e41 Compare March 19, 2026 03:14
@github-actions
github-actions Bot force-pushed the changeset-release/main branch 2 times, most recently from b46ad56 to b918b43 Compare March 25, 2026 17:34
@kilo-code-bot

kilo-code-bot Bot commented Mar 25, 2026

Copy link
Copy Markdown

Kilo Code Review could not run — your account is out of credits.

Add credits at app.kilo.ai to enable reviews on this change.

@github-actions
github-actions Bot force-pushed the changeset-release/main branch 3 times, most recently from 1265e1f to 08db8db Compare March 31, 2026 09:09
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 08db8db to 936892a Compare April 6, 2026 11:20
@kilo-code-bot

kilo-code-bot Bot commented Apr 6, 2026

Copy link
Copy Markdown

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (5 files)
  • .changeset/common-items-fix.md - changeset file for adding prerelease support
  • .changeset/pre.json - changeset list update
  • libs/langgraph-cli/CHANGELOG.md - changelog entry for the feature
  • libs/langgraph-cli/src/utils/config.mts - updated api_version validation regex and message
  • libs/langgraph-cli/tests/config.test.mts - updated tests to use compact prerelease format and reject hyphen format

Reviewed by gemma-4-26b-a4b-it · 3,874 tokens

@github-actions
github-actions Bot force-pushed the changeset-release/main branch 2 times, most recently from 5a8ac63 to 2296400 Compare April 15, 2026 10:59
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 2296400 to a7b0c9d Compare May 9, 2026 11:38
@github-actions github-actions Bot changed the title chore: version packages chore: version packages (rc) May 13, 2026
@github-actions
github-actions Bot force-pushed the changeset-release/main branch 3 times, most recently from e624be2 to 4b4b041 Compare May 16, 2026 11:52
@github-actions github-actions Bot changed the title chore: version packages (rc) chore: version packages May 29, 2026
@github-actions
github-actions Bot force-pushed the changeset-release/main branch 3 times, most recently from c5fab3e to a6f9738 Compare June 1, 2026 13:13
@github-actions
github-actions Bot force-pushed the changeset-release/main branch 3 times, most recently from ed32d41 to a583586 Compare June 12, 2026 04:43
@github-actions
github-actions Bot force-pushed the changeset-release/main branch 3 times, most recently from f042f32 to 8cea3a3 Compare June 17, 2026 21:30
@github-actions
github-actions Bot force-pushed the changeset-release/main branch 4 times, most recently from 84a7832 to 6bb03e6 Compare June 24, 2026 15:44
@github-actions
github-actions Bot force-pushed the changeset-release/main branch 2 times, most recently from 872c5fb to 74f4244 Compare July 5, 2026 16:09
@github-actions
github-actions Bot force-pushed the changeset-release/main branch 3 times, most recently from 3a12d71 to 1b36638 Compare August 25, 2026 11:28
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 1b36638 to ced9484 Compare August 27, 2026 06:47
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from ced9484 to 2596b5d Compare September 12, 2026 04:53
@coderabbitai

coderabbitai Bot commented Sep 12, 2026

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 4f8f845f-d802-413b-b3e8-024f05525409

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

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