[dependabot]

Bumps the minor-and-patch group with 25 updates:

Package	From	To
@langchain/core	1.2.17	1.2.18
@langchain/langgraph	1.4.21	1.5.0
@langchain/langgraph-sdk	1.12.3	1.12.4
@radix-ui/react-avatar	1.2.7	1.3.1
@radix-ui/react-dialog	1.2.0	1.3.1
@radix-ui/react-label	2.1.16	2.1.17
@radix-ui/react-separator	1.1.16	1.2.0
@radix-ui/react-slot	1.4.0	1.5.0
@radix-ui/react-switch	1.3.8	1.4.1
@radix-ui/react-tooltip	1.3.0	1.4.1
framer-motion	14.0.0	14.3.0
lucide-react	1.53.0	1.57.0
react	19.3.0	19.3.1
react-dom	19.3.0	19.3.1
uuid	14.0.2	14.0.3
zod	4.6.5	4.6.7
@playwright/test	1.64.0	1.64.1
@types/lodash	4.17.25	4.17.26
@types/node	26.6.4	26.6.5
dotenv	18.0.6	18.0.8
eslint-config-next	16.4.0	16.4.2
next	16.4.0	16.4.2
postcss	8.5.29	8.5.30
prettier	3.9.9	3.9.10
typescript-eslint	8.71.1	8.71.2

Updates @langchain/core from 1.2.17 to 1.2.18

Release notes

Sourced from @​langchain/core's releases.

@​langchain/core@​1.2.18

Patch Changes

• #11956 93d62b0 Thanks @​hntrl! - Require langsmith >=0.11.0 to include the restored NullableHeaders type declarations.

• #11822 d3e6fe6 Thanks @​dqbd! - Add explicit agent address support to LangChainTracer, inherit project and address destinations together, and delegate default destination resolution to the LangSmith SDK.

• #11150 cea15cf Thanks @​mdnanocom! - fix(core): defer tool call chunk collapsing in AIMessageChunk to fix O(n²) streaming aggregation

  AIMessageChunk eagerly re-ran collapseToolCallChunks in its constructor on every streamed delta concat, re-parsing all accumulated tool args each time — O(n²) over a stream, which can block the event loop for seconds on long tool-call streams. Collapsing now runs lazily, once, on first read of tool_calls / invalid_tool_calls.

Commits

• ba363b1 chore: version packages (#11937)
• 93d62b0 fix: require langsmith with restored header declarations (#11956)
• 57d0e02 fix(google): support Argon thinking and preserve streaming usage (#11940)
• 73a739c feat(aws): map Bedrock thinking tokens to output_token_details.reasoning (#11...
• 227f01c feat(langchain): support HITL respond decisions (#11498)
• d3e6fe6 feat(core): add explicit address support to LangChainTracer (#11822)
• cea15cf fix(core): defer tool call chunk collapsing in AIMessageChunk to fix O(n²) st...
• 20c38bf fix: bump vulnerable transitive dependencies (#11920)
• b2c1134 chore: version packages (#11881)
• aa1b519 docs: fix typo in README (#11443)
• Additional commits viewable in compare view

Updates @langchain/langgraph from 1.4.21 to 1.5.0

Release notes

Sourced from @​langchain/langgraph's releases.

@​langchain/langgraph-api@​1.5.0

Minor Changes

• #2850 48245a8 Thanks @​casparb! - Pass a typed ServerRuntime as the second graph factory argument. Runs and resumes receive executionRuntime.context; assistant inspection and thread state operations receive executionRuntime: null. Existing config-only factories remain supported.

Patch Changes

• Updated dependencies []:
  • @​langchain/langgraph-ui@​1.5.0

@​langchain/langgraph-cli@​1.5.0

Patch Changes

• Updated dependencies [48245a8]:
  • @​langchain/langgraph-api@​1.5.0

@​langchain/langgraph-ui@​1.5.0

No changes in this release.

@​langchain/langgraph-checkpoint-mongodb@​1.5.0

Minor Changes

• #2961 1631fd8 Thanks @​soarez! - order parallel writes by task path, like langgraph (Python) — one sort key for live execution and every saver, instead of the task-id order #2544 added for DeltaChannel writes

  When two or more tasks in one superstep write the same DeltaChannel, their writes are now applied and replayed in (task_path, task_id, idx) order — the order Python's langgraph#8544 established — instead of task-id order. Task ids are uuid5 hashes that include the checkpoint id, so the old order permuted parallel writers from run to run and disagreed with Python.

  • BaseCheckpointSaver.putWrites takes an optional taskPath (the serialized task path, taskPathStr), and getTuple/list must return pendingWrites in the new writesSortKey order. writesSortKey and compareWritesSortKeys are new exports of @langchain/langgraph-checkpoint; every saver (memory, SQLite, Postgres, Redis incl. ShallowRedisSaver, MongoDB) stores the path and sorts in JS — no database collation is involved.
  • SQLite and Postgres gain a task_path column (migrated automatically on setup(); read-only pre-column SQLite databases keep reading, with their rows keeping the old order). Redis and MongoDB documents gain a task_path field. Rows written before the upgrade keep their old order.
  • Exit-durability resumes replay delta writes in live order (port of langgraph#9114): the resumed superstep's writes interleave with the loaded ones by task path, later supersteps sort after every real write, and writes loaded with the checkpoint are no longer stored twice.
  • bulkUpdateState seals the first update superstep: DeltaChannels touched by the base checkpoint's pending writes (and whose version moved) snapshot on the update checkpoint, so a finished sibling's writes and the update's can't replay in the wrong order (partial port of langgraph#8548).
  • bulkUpdateState/updateState update tasks carry (__interrupt__, i) task paths, as in langgraph#9128, so several updates in one superstep writing the same DeltaChannel replay in the order given.
  • Send task paths become [PUSH, i, false] and node-error-handler paths become [*failedTask.path[:3], "node_error_handler", false] (the failed task's first three path elements), matching Python's shapes — langgraph_path task metadata changes accordingly, and task ids of functional task() calls under a Send or handler task change with them. The SDK's Send-task detection accepts both the old and new shapes.

  Upgrade notes:

  • PostgresSaver: run setup() once after upgrading, from one process, before the new version serves traffic. The task_path column comes from the first new migration since the saver shipped, and until it runs, reads and writes fail with column "task_path" does not exist. Several processes running setup() at once on a database that still needs the migration can fail with a duplicate key error on checkpoint_migrations.
  • Third-party checkpoint savers remain source-compatible but must now persist the taskPath they are given and return pendingWrites in writesSortKey order; the conformance suite's new base tests enforce this. A saver that ignores the new argument replays in task-id order and can rebuild a different DeltaChannel value than the run produced.
  • An incomplete superstep containing stored delta writes that must interleave with resumed or retried task writes is affected by the upgrade, whether the incompleteness came from an interrupt, a task error, a crash, or a drain: finish such threads with the old runtime before upgrading writers. A single interrupted node with no finished delta-writing siblings is safe to resume. The same applies to resuming work that includes functional task() calls under a Send or error-handler task, whose child task ids change.
  • @langchain/langgraph-checkpoint 1.2.0 must be released before any package requiring its new exports; the consumers' minimum ranges are raised accordingly.

@​langchain/langgraph@​1.5.0

Minor Changes

• #2961 1631fd8 Thanks @​soarez! - order parallel writes by task path, like langgraph (Python) — one sort key for live execution and every saver, instead of the task-id order #2544 added for DeltaChannel writes

  When two or more tasks in one superstep write the same DeltaChannel, their writes are now applied and replayed in (task_path, task_id, idx) order — the order Python's langgraph#8544 established — instead of task-id order. Task ids are uuid5 hashes that include the checkpoint id, so the old order permuted parallel writers from run to run and disagreed with Python.

  • BaseCheckpointSaver.putWrites takes an optional taskPath (the serialized task path, taskPathStr), and getTuple/list must return pendingWrites in the new writesSortKey order. writesSortKey and compareWritesSortKeys are new exports of @langchain/langgraph-checkpoint; every saver (memory, SQLite, Postgres, Redis incl. ShallowRedisSaver, MongoDB) stores the path and sorts in JS — no database collation is involved.
  • SQLite and Postgres gain a task_path column (migrated automatically on setup(); read-only pre-column SQLite databases keep reading, with their rows keeping the old order). Redis and MongoDB documents gain a task_path field. Rows written before the upgrade keep their old order.
  • Exit-durability resumes replay delta writes in live order (port of langgraph#9114): the resumed superstep's writes interleave with the loaded ones by task path, later supersteps sort after every real write, and writes loaded with the checkpoint are no longer stored twice.

... (truncated)

Changelog

Sourced from @​langchain/langgraph's changelog.

1.5.0

Minor Changes

• #2961 1631fd8 Thanks @​soarez! - order parallel writes by task path, like langgraph (Python) — one sort key for live execution and every saver, instead of the task-id order #2544 added for DeltaChannel writes

  When two or more tasks in one superstep write the same DeltaChannel, their writes are now applied and replayed in (task_path, task_id, idx) order — the order Python's langgraph#8544 established — instead of task-id order. Task ids are uuid5 hashes that include the checkpoint id, so the old order permuted parallel writers from run to run and disagreed with Python.

  • BaseCheckpointSaver.putWrites takes an optional taskPath (the serialized task path, taskPathStr), and getTuple/list must return pendingWrites in the new writesSortKey order. writesSortKey and compareWritesSortKeys are new exports of @langchain/langgraph-checkpoint; every saver (memory, SQLite, Postgres, Redis incl. ShallowRedisSaver, MongoDB) stores the path and sorts in JS — no database collation is involved.
  • SQLite and Postgres gain a task_path column (migrated automatically on setup(); read-only pre-column SQLite databases keep reading, with their rows keeping the old order). Redis and MongoDB documents gain a task_path field. Rows written before the upgrade keep their old order.
  • Exit-durability resumes replay delta writes in live order (port of langgraph#9114): the resumed superstep's writes interleave with the loaded ones by task path, later supersteps sort after every real write, and writes loaded with the checkpoint are no longer stored twice.
  • bulkUpdateState seals the first update superstep: DeltaChannels touched by the base checkpoint's pending writes (and whose version moved) snapshot on the update checkpoint, so a finished sibling's writes and the update's can't replay in the wrong order (partial port of langgraph#8548).
  • bulkUpdateState/updateState update tasks carry (__interrupt__, i) task paths, as in langgraph#9128, so several updates in one superstep writing the same DeltaChannel replay in the order given.
  • Send task paths become [PUSH, i, false] and node-error-handler paths become [*failedTask.path[:3], "node_error_handler", false] (the failed task's first three path elements), matching Python's shapes — langgraph_path task metadata changes accordingly, and task ids of functional task() calls under a Send or handler task change with them. The SDK's Send-task detection accepts both the old and new shapes.

  Upgrade notes:

  • PostgresSaver: run setup() once after upgrading, from one process, before the new version serves traffic. The task_path column comes from the first new migration since the saver shipped, and until it runs, reads and writes fail with column "task_path" does not exist. Several processes running setup() at once on a database that still needs the migration can fail with a duplicate key error on checkpoint_migrations.
  • Third-party checkpoint savers remain source-compatible but must now persist the taskPath they are given and return pendingWrites in writesSortKey order; the conformance suite's new base tests enforce this. A saver that ignores the new argument replays in task-id order and can rebuild a different DeltaChannel value than the run produced.
  • An incomplete superstep containing stored delta writes that must interleave with resumed or retried task writes is affected by the upgrade, whether the incompleteness came from an interrupt, a task error, a crash, or a drain: finish such threads with the old runtime before upgrading writers. A single interrupted node with no finished delta-writing siblings is safe to resume. The same applies to resuming work that includes functional task() calls under a Send or error-handler task, whose child task ids change.
  • @langchain/langgraph-checkpoint 1.2.0 must be released before any package requiring its new exports; the consumers' minimum ranges are raised accordingly.

Patch Changes

• #2980 5c81e5f Thanks @​eliornl! - A node served from the node cache now saves its writes like a node that ran. They were applied but never saved, so a DeltaChannel read back without them once the state was loaded again, under every durability. A cache hit is still streamed as cached and isn't written back to the cache.

• #2989 7789c52 Thanks @​eliornl! - An exit-durability run that starts from a checkpoint the thread has moved past, addressed by checkpoint_id, no longer stores its DeltaChannel writes on that checkpoint, where the branch that already grew from it read them too. The run now snapshots the channels it wrote instead.

• #2969 5a4f831 Thanks @​eliornl! - fix(langgraph): a checkpoint save now waits for the DeltaChannel writes the run sent before it and is skipped if one of them failed, so a failed write no longer leaves the channel reading back without it.

• #2974 0dc519c Thanks @​eliornl! - fix(langgraph): a DeltaChannel no longer reads back writes from another branch. The first checkpoint of a new branch snapshots the delta channels its base has pending writes for, an updateState on a checkpoint the thread moved past stores none of its writes there, and a replay of such a checkpoint forks before storing a Command's writes.

• #2981 3f763ae Thanks @​eliornl! - A run's input to a DeltaChannel input channel of a raw Pregel graph reads back only on the checkpoints built from it. With "sync" or "async" durability it was saved as the starting checkpoint's own state: on a new thread the first run's input was lost, the previous run's last checkpoint read the next run's input, and a run from an older checkpoint leaked its input into the branch that already grew from it. Now the input is stored on the starting checkpoint under its own task id, or, on a new thread or an addressed checkpoint, the input checkpoint snapshots the channel. Threads saved before this keep the input already stored on their checkpoints.

• #2983 f9cfb1e Thanks @​eliornl! - A fork from a checkpoint before a DeltaChannel's first write no longer starts the channel's subscribers that never ran. The fork's snapshot gave the channel its first version, and a node subscribed to it ran on the empty value before the node that writes it.

• #2973 800ed57 Thanks @​eliornl! - fix(langgraph): updateState saves counters_since_delta_snapshot on every checkpoint it creates, so the next run keeps counting from it instead of from zero and DeltaChannels snapshot on schedule after an update.

• #2982 7a01526 Thanks @​eliornl! - An Overwrite through updateState snapshots the DeltaChannel it resets on the checkpoint the update saves, as a node's Overwrite does in the loop. The value already read back right; reads of that checkpoint and the ones after it no longer walk back past the reset.

• #3009 f07064c Thanks @​soarez! - A drain requested right before an interruptBefore breakpoint now stops the run at the breakpoint. The run used to drain there instead, and resuming it with invoke(null, config) ran past the breakpoint, since a resume treats the next step's breakpoints as already passed.

• #2968 8aa37d4 Thanks @​eliornl! - fix(langgraph): exit-mode DeltaChannel writes are never stored under the null task id. A run that started at step 0 with a Command update, such as a new thread started with Command({ update, goto }) under durability: "exit", stored the update under NULL_TASK_ID, so reading or replaying that first checkpoint applied it to the DeltaChannel but not to plain channels.

• #2975 f8e2c8b Thanks @​eliornl! - fix(langgraph): channels written in one step share one version again: _applyWrites mints each version once. A saver that adds a random fraction to its versions, as the Postgres and Redis savers now do, gave each channel its own, so updateState without asNode after two parallel nodes applied the update as either one instead of throwing "Ambiguous update".

• #2969 5a4f831 Thanks @​eliornl! - Prevent checkpointer write failures from surfacing as process-level unhandledRejection events before the run boundary reports them.

• #2992 13d848e Thanks @​eliornl! - Give every message written to a DeltaChannel that uses messagesDeltaReducer an id, so RemoveMessage can target it: one saved through updateState, a string, a [role, content] pair, a plain object, one inside an Overwrite, a raw Pregel input, or a Command forked from an older checkpoint.

• Updated dependencies [e827007, 50f1490, 1631fd8, 55902f3]:

... (truncated)

Commits

• 4510774 chore: version packages (#2977)
• 13d848e fix(langgraph): give every message written to a messages DeltaChannel an id (...
• f07064c fix(langgraph): stop at an interruptBefore breakpoint when a drain is request...
• f8e2c8b fix(langgraph-checkpoint-postgres): keep two branches from sharing a channel ...
• 7789c52 fix(langgraph): keep an exit run from a checkpoint the thread moved past out ...
• f9cfb1e fix(langgraph): keep a fork's DeltaChannel snapshot from starting nodes that ...
• 3f763ae fix(langgraph): read a run's DeltaChannel input back only on its own checkpoi...
• 7a01526 fix(langgraph): snapshot a DeltaChannel that an updateState Overwrite resets ...
• 5a4f831 fix(langgraph): don't save a checkpoint past a failed DeltaChannel write (#2969)
• 0dc519c fix(langgraph): keep a DeltaChannel branch from replaying another branch's wr...
• Additional commits viewable in compare view

Updates @langchain/langgraph-sdk from 1.12.3 to 1.12.4

Release notes

Sourced from @​langchain/langgraph-sdk's releases.

@​langchain/langgraph-sdk@​1.12.4

Patch Changes

• #2961 1631fd8 Thanks @​soarez! - order parallel writes by task path, like langgraph (Python) — one sort key for live execution and every saver, instead of the task-id order #2544 added for DeltaChannel writes

  When two or more tasks in one superstep write the same DeltaChannel, their writes are now applied and replayed in (task_path, task_id, idx) order — the order Python's langgraph#8544 established — instead of task-id order. Task ids are uuid5 hashes that include the checkpoint id, so the old order permuted parallel writers from run to run and disagreed with Python.

  • BaseCheckpointSaver.putWrites takes an optional taskPath (the serialized task path, taskPathStr), and getTuple/list must return pendingWrites in the new writesSortKey order. writesSortKey and compareWritesSortKeys are new exports of @langchain/langgraph-checkpoint; every saver (memory, SQLite, Postgres, Redis incl. ShallowRedisSaver, MongoDB) stores the path and sorts in JS — no database collation is involved.
  • SQLite and Postgres gain a task_path column (migrated automatically on setup(); read-only pre-column SQLite databases keep reading, with their rows keeping the old order). Redis and MongoDB documents gain a task_path field. Rows written before the upgrade keep their old order.
  • Exit-durability resumes replay delta writes in live order (port of langgraph#9114): the resumed superstep's writes interleave with the loaded ones by task path, later supersteps sort after every real write, and writes loaded with the checkpoint are no longer stored twice.
  • bulkUpdateState seals the first update superstep: DeltaChannels touched by the base checkpoint's pending writes (and whose version moved) snapshot on the update checkpoint, so a finished sibling's writes and the update's can't replay in the wrong order (partial port of langgraph#8548).
  • bulkUpdateState/updateState update tasks carry (__interrupt__, i) task paths, as in langgraph#9128, so several updates in one superstep writing the same DeltaChannel replay in the order given.
  • Send task paths become [PUSH, i, false] and node-error-handler paths become [*failedTask.path[:3], "node_error_handler", false] (the failed task's first three path elements), matching Python's shapes — langgraph_path task metadata changes accordingly, and task ids of functional task() calls under a Send or handler task change with them. The SDK's Send-task detection accepts both the old and new shapes.

  Upgrade notes:

  • PostgresSaver: run setup() once after upgrading, from one process, before the new version serves traffic. The task_path column comes from the first new migration since the saver shipped, and until it runs, reads and writes fail with column "task_path" does not exist. Several processes running setup() at once on a database that still needs the migration can fail with a duplicate key error on checkpoint_migrations.
  • Third-party checkpoint savers remain source-compatible but must now persist the taskPath they are given and return pendingWrites in writesSortKey order; the conformance suite's new base tests enforce this. A saver that ignores the new argument replays in task-id order and can rebuild a different DeltaChannel value than the run produced.
  • An incomplete superstep containing stored delta writes that must interleave with resumed or retried task writes is affected by the upgrade, whether the incompleteness came from an interrupt, a task error, a crash, or a drain: finish such threads with the old runtime before upgrading writers. A single interrupted node with no finished delta-writing siblings is safe to resume. The same applies to resuming work that includes functional task() calls under a Send or error-handler task, whose child task ids change.
  • @langchain/langgraph-checkpoint 1.2.0 must be released before any package requiring its new exports; the consumers' minimum ranges are raised accordingly.

Changelog

Sourced from @​langchain/langgraph-sdk's changelog.

1.12.4

Patch Changes

• #2961 1631fd8 Thanks @​soarez! - order parallel writes by task path, like langgraph (Python) — one sort key for live execution and every saver, instead of the task-id order #2544 added for DeltaChannel writes

  When two or more tasks in one superstep write the same DeltaChannel, their writes are now applied and replayed in (task_path, task_id, idx) order — the order Python's langgraph#8544 established — instead of task-id order. Task ids are uuid5 hashes that include the checkpoint id, so the old order permuted parallel writers from run to run and disagreed with Python.

  • BaseCheckpointSaver.putWrites takes an optional taskPath (the serialized task path, taskPathStr), and getTuple/list must return pendingWrites in the new writesSortKey order. writesSortKey and compareWritesSortKeys are new exports of @langchain/langgraph-checkpoint; every saver (memory, SQLite, Postgres, Redis incl. ShallowRedisSaver, MongoDB) stores the path and sorts in JS — no database collation is involved.
  • SQLite and Postgres gain a task_path column (migrated automatically on setup(); read-only pre-column SQLite databases keep reading, with their rows keeping the old order). Redis and MongoDB documents gain a task_path field. Rows written before the upgrade keep their old order.
  • Exit-durability resumes replay delta writes in live order (port of langgraph#9114): the resumed superstep's writes interleave with the loaded ones by task path, later supersteps sort after every real write, and writes loaded with the checkpoint are no longer stored twice.
  • bulkUpdateState seals the first update superstep: DeltaChannels touched by the base checkpoint's pending writes (and whose version moved) snapshot on the update checkpoint, so a finished sibling's writes and the update's can't replay in the wrong order (partial port of langgraph#8548).
  • bulkUpdateState/updateState update tasks carry (__interrupt__, i) task paths, as in langgraph#9128, so several updates in one superstep writing the same DeltaChannel replay in the order given.
  • Send task paths become [PUSH, i, false] and node-error-handler paths become [*failedTask.path[:3], "node_error_handler", false] (the failed task's first three path elements), matching Python's shapes — langgraph_path task metadata changes accordingly, and task ids of functional task() calls under a Send or handler task change with them. The SDK's Send-task detection accepts both the old and new shapes.

  Upgrade notes:

  • PostgresSaver: run setup() once after upgrading, from one process, before the new version serves traffic. The task_path column comes from the first new migration since the saver shipped, and until it runs, reads and writes fail with column "task_path" does not exist. Several processes running setup() at once on a database that still needs the migration can fail with a duplicate key error on checkpoint_migrations.
  • Third-party checkpoint savers remain source-compatible but must now persist the taskPath they are given and return pendingWrites in writesSortKey order; the conformance suite's new base tests enforce this. A saver that ignores the new argument replays in task-id order and can rebuild a different DeltaChannel value than the run produced.
  • An incomplete superstep containing stored delta writes that must interleave with resumed or retried task writes is affected by the upgrade, whether the incompleteness came from an interrupt, a task error, a crash, or a drain: finish such threads with the old runtime before upgrading writers. A single interrupted node with no finished delta-writing siblings is safe to resume. The same applies to resuming work that includes functional task() calls under a Send or error-handler task, whose child task ids change.
  • @langchain/langgraph-checkpoint 1.2.0 must be released before any package requiring its new exports; the consumers' minimum ranges are raised accordingly.

Commits

• 4510774 chore: version packages (#2977)
• 1631fd8 fix(langgraph): order parallel writes by task path, like langgraph (Python) (...
• See full diff in compare view

Updates @radix-ui/react-avatar from 1.2.7 to 1.3.1

Changelog

Sourced from @​radix-ui/react-avatar's changelog.

1.3.1

• Fixed a type regression where callback props that were previously declared as methods rejected handlers whose parameter is narrower than the prop's.

1.3.0

• Allow explicit undefined for all optional types for compatibility with TypeScript's exactOptionalPropertyTypes flag.
• Updated dependencies: @radix-ui/primitive@1.2.0, @radix-ui/react-context@1.3.0, @radix-ui/react-primitive@2.2.0, @radix-ui/react-use-callback-ref@1.1.5

Commits

• See full diff in compare view

Updates @radix-ui/react-dialog from 1.2.0 to 1.3.1

Changelog

Sourced from @​radix-ui/react-dialog's changelog.

1.3.1

• Fixed a type regression where callback props that were previously declared as methods rejected handlers whose parameter is narrower than the prop's.
• Updated dependencies: @radix-ui/react-dismissable-layer@1.2.1, @radix-ui/react-focus-scope@1.3.1

1.3.0

• Allow explicit undefined for all optional types for compatibility with TypeScript's exactOptionalPropertyTypes flag.
• Updated dependencies: @radix-ui/primitive@1.2.0, @radix-ui/react-context@1.3.0, @radix-ui/react-dismissable-layer@1.2.0, @radix-ui/react-focus-guards@1.2.0, @radix-ui/react-focus-scope@1.3.0, @radix-ui/react-portal@1.2.0, @radix-ui/react-primitive@2.2.0, @radix-ui/react-slot@1.5.0, @radix-ui/react-use-controllable-state@1.3.0

Commits

• See full diff in compare view

Updates @radix-ui/react-label from 2.1.16 to 2.1.17

Changelog

Sourced from @​radix-ui/react-label's changelog.

2.1.17

• Updated dependencies: @radix-ui/react-primitive@2.2.0

Commits

• See full diff in compare view

Updates @radix-ui/react-separator from 1.1.16 to 1.2.0

Changelog

Sourced from @​radix-ui/react-separator's changelog.

1.2.0

• Allow explicit undefined for all optional types for compatibility with TypeScript's exactOptionalPropertyTypes flag.
• Updated dependencies: @radix-ui/react-primitive@2.2.0

Commits

• See full diff in compare view

Updates @radix-ui/react-slot from 1.4.0 to 1.5.0

Changelog

Sourced from @​radix-ui/react-slot's changelog.

1.5.0

• Allow explicit undefined for all optional types for compatibility with TypeScript's exactOptionalPropertyTypes flag.
• Fixed Slot throwing when an asChild child is a lazy reference whose resolved value is itself a lazy reference.

Commits

• See full diff in compare view

Updates @radix-ui/react-switch from 1.3.8 to 1.4.1

Changelog

Sourced from @​radix-ui/react-switch's changelog.

1.4.1

• Fixed a type regression where callback props that were previously declared as methods rejected handlers whose parameter is narrower than the prop's.

1.4.0

• Allow explicit undefined for all optional types for compatibility with TypeScript's exactOptionalPropertyTypes flag.
• Fixed bugs in form-nested control components where a user-driven change was treated as programmatic in some cases, preventing bubbled event handlers from being called.
• Updated dependencies: @radix-ui/primitive@1.2.0, @radix-ui/react-context@1.3.0, @radix-ui/react-primitive@2.2.0, @radix-ui/react-use-controllable-state@1.3.0

Commits

• See full diff in compare view

Updates @radix-ui/react-tooltip from 1.3.0 to 1.4.1

Changelog

Sourced from @​radix-ui/react-tooltip's changelog.

1.4.1

• Fixed a type regression where callback props that were previously declared as methods rejected handlers whose parameter is narrower than the prop's.
• Updated dependencies: @radix-ui/react-dismissable-layer@1.2.1, @radix-ui/react-focus-scope@1.3.1

1.4.0

• Allow explicit undefined for all optional types for compatibility with TypeScript's exactOptionalPropertyTypes flag.
• Fixed a bug where tabbing away from a focusable tooltip trigger nested in a modal popover moved focus to the popover's root instead of the next element in the popover.
• Updated dependencies: @radix-ui/primitive@1.2.0, @radix-ui/react-context@1.3.0, @radix-ui/react-dismissable-layer@1.2.0, @radix-ui/react-focus-scope@1.3.0, @radix-ui/react-popper@1.4.0, @radix-ui/react-portal@1.2.0, @radix-ui/react-primitive@2.2.0, @radix-ui/react-slot@1.5.0, @radix-ui/react-use-controllable-state@1.3.0, @radix-ui/react-visually-hidden@1.2.13

Commits

• See full diff in compare view

Updates framer-motion from 14.0.0 to 14.3.0

Changelog

Sourced from framer-motion's changelog.

[14.3.0] 2026-10-15

Added

• stagger: New grid, from: "edges" | "random" options.
• Support for scaleZ.

Fixed

• Fix matrix3d and other digit-named transform functions being tokenised as numbers.
• useSpring: Ensure when switching targets we animate to the new target on switch.
• Fix SVG MotionValue children being written as a children attribute.
• AnimatePresence: Fire onExitComplete after exiting children unmount.
• AnimatePresence: popLayout children that don't accept ref are now popped when root component is <motion> element.
• Fix interpolation of axis rotate and skew transforms during shared layout animation.
• Fix layout animations when layout is enabled after mount.
• Fix drag jumping to 0 after animate x/y to CSS variable.
• arc: Fix path animations with animate.
• Ensure shared elements are freed from memory when unmounted.
• Fix accelerated independent transform animations vanishing when they start from a float residue.

[14.2.0] 2026-10-13

Added

• Hardware accelerated independent transforms like x, y, scaleX etc.

[14.1.1] 2026-10-13

Fixed

• Fix velocity hand-off for hardware-accelerated springs.
• cubicBezier: More accurate, 2x faster.
• Reorder: Fix click events on reoredered items.
• useTransform: Fix desync when source is set in an effect under Strict Mode.

[14.1.0] 2026-10-09

Added

• animateLayout: Layout animations for vanilla JS.

Fixed

• Delay animation start when main thread held to prevent visual jumps.
• Fix whileHover/whileTap getting stuck after Fast Refresh reorders siblings.
• scroll/useScroll: Fix reporting of elastic overscroll.
• AnimatePresence: Fix popLayout when rendering into another window or iframe.
• animate: Fix JS animations jumping ahead when played after a pause at non-1 speed.
• Allow layout animations inside dragged elements.

Commits

• 0403bee v14.3.0
• 33a7ae0 Latest
• a1fdaa7 Merge pull request #3927 from motiondivision/claude/project-thread-q79mtn-iss...
• a81eb89 Merge pull request #3924 from motiondivision/claude/project-thread-q79mtn-iss...
• 81738d3 Fix scaleZ not being applied to the transform
• a26b026 Fix SVG MotionValue children being written as a children attribute
• 0caa412 Add failing test for #2609: scaleZ is not applied to the transform
• 81d8aae Add failing test for #2578: motion.text writes MotionValue child as attribute
• 2b68ca9 latest
• 5b53571 Updating changelog
• Additional commits viewable in compare view

Updates lucide-react from 1.53.0 to 1.57.0

Release notes

Sourced from lucide-react's releases.

Version 1.57.0

What's Changed

• feat(icons): added folder-user and folder-user icons by @​rrod497 in lucide-icons/lucide#4603
• feat(icons): added calendar-chevrons-left icon by @​karsa-mistmere in lucide-icons/lucide#5001
• feat(icons): added users-collaboration icon by @​rrod497 in lucide-icons/lucide#4922
• feat(icons): added Belarusian ruble icon by @​js-best in lucide-icons/lucide#4984
• feat(icons): added circle-fading-play icon by @​tatianatsiguleva in lucide-icons/lucide#4990
• feat(icons): add cpu-ai icon by @​signalgridco in lucide-icons/lucide#4992
• feat(icons): added guitar-electric icon by @​rrod497 in lucide-icons/lucide#4917
• feat(icons): added graph-star icon by @​Nitero in lucide-icons/lucide#4983
• chore(deps-dev): bump the svelte-deps group with 2 updates by @​dependabot[bot] in lucide-icons/lucide#4996
• chore(deps-dev): bump preact from 11.0.0 to 11.0.1 in the preact-deps group by @​dependabot[bot] in lucide-icons/lucide#4999
• chore(deps-dev): bump @​vitejs/plugin-react from 6.1.1 to 6.1.2 in the react-deps group by @​dependabot[bot] in lucide-icons/lucide#4995
• feat(icons): added perfume icon by @​rrod497 in lucide-icons/lucide#4426

New Contributors

• @​js-best made their first contribution in lucide-icons/lucide#4984
• @​tatianatsiguleva made their first contribution in lucide-icons/lucide#4990
• @​signalgridco made their first contribution in lucide-icons/lucide#4992
• @​Nitero made their first contribution in lucide-icons/lucide#4983

Full Changelog: lucide-icons/lucide@1.56.0...1.57.0

Version 1.56.0

What's Changed

• feat(icons): added server-nas icon by @​benhaube in lucide-icons/lucide#4537
• fix(icons,categories): fix notifications category name and refine circle-x tags by @​Rachit315 in lucide-icons/lucide#4994
• feat(icons): add message-circle-text icon by @​ericfennis in lucide-icons/lucide#4898

New Contributors

• @​Rachit315 made their first contribution in lucide-icons/lucide#4994

Full Changelog: lucide-icons/lucide@1.55.0...1.56.0

Version 1.55.0

What's Changed

• feat(icons): added mail-dot icon by @​elenakovelskikh in lucide-icons/lucide#3230
• ci(lint): split lint jobs and annotate Prettier and JSON schema errors in PRs by @​ericfennis in lucide-icons/lucide#4982
• chore(deps-dev): bump sharp from 0.35.4 to 0.35.5 by @​dependabot[bot] in lucide-icons/lucide#4987
• chore(deps): bump next from 16.3.6 to 16.3.8 by @​dependabot[bot] in lucide-icons/lucide#4988
• test(lucide): add tests for empty icons error and DocumentFragment root in createIcons by @​grzdev in lucide-icons/lucide#4967
• feat(icons): added phone-log icon by @​Levi-Bensley in lucide-icons/lucide#3598
• chore(copilot-instruction): Adjust instruction text to allow more then 4 use-cases by @​ericfennis in lucide-icons/lucide#4989
• feat(icons): added wifi-lock icon by @​benhaube in lucide-icons/lucide#4913
• feat(icons): Add handle-bottom-right icon by @​ocavue in lucide-icons/lucide#1793
• test(lucide-react): add tests for DynamicIcon fallback and ref forwarding by @​grzdev in lucide-icons/lucide#4966
• feat(icons): added screw icon by @​edik17 in lucide-icons/lucide#4932
• feat(icons): added user-round-star icon by @​karsa-mistmere in lucide-icons/lucide#3469
• feat(icons): added shield-house icon by @​benhaube in lucide-icons/lucide#4602

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
langgraph-chat	Ready	Preview	Oct 19, 2026 1:02am UTC

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	next@​16.4.0 ⏵ 16.4.2	+1		+1
	@​radix-ui/​react-label@​2.1.16 ⏵ 2.1.17
	@​radix-ui/​react-separator@​1.1.16 ⏵ 1.2.0
	eslint-config-next@​16.4.0 ⏵ 16.4.2
	@​radix-ui/​react-slot@​1.4.0 ⏵ 1.5.0	+1		+1
	@​radix-ui/​react-avatar@​1.2.7 ⏵ 1.3.1			+1
	@​radix-ui/​react-switch@​1.3.8 ⏵ 1.4.1			+1
	@​radix-ui/​react-dialog@​1.2.0 ⏵ 1.3.1	+1		+1
	@​radix-ui/​react-tooltip@​1.3.0 ⏵ 1.4.1			+1
	@​langchain/​langgraph-sdk@​1.12.3 ⏵ 1.12.4
	typescript-eslint@​8.71.1 ⏵ 8.71.2
	@​types/​lodash@​4.17.25 ⏵ 4.17.26				-1
	lucide-react@​1.53.0 ⏵ 1.57.0	+1		+1	+1
	postcss@​8.5.29 ⏵ 8.5.30	+1		+1
	react@​19.3.0 ⏵ 19.3.1
	uuid@​14.0.2 ⏵ 14.0.3				+2
	react-dom@​19.3.0 ⏵ 19.3.1			+1
	@​langchain/​langgraph@​1.4.21 ⏵ 1.5.0			+1
	zod@​4.6.5 ⏵ 4.6.7
	@​langchain/​core@​1.2.17 ⏵ 1.2.18			+1	-1
	dotenv@​18.0.6 ⏵ 18.0.8	+1		+1	+1
	prettier@​3.9.9 ⏵ 3.9.10
	framer-motion@​14.0.0 ⏵ 14.3.0			+1
	@​playwright/​test@​1.64.0 ⏵ 1.64.1

View full report

[John Kennedy (jkennedyvz)]

Approved dependency update; checks passing and merge requirements satisfied.