ca7790f895
## Description Fixed `BaseCallbackManager.merge()` method to correctly preserve the distinction between `handlers` and `inheritable_handlers` during merge operations. Previously, the merge method was using `add_handler()` which incorrectly added handlers to both lists when `inherit=True`, causing cross-contamination between regular and inheritable handlers. The fix directly passes the combined handler lists to the constructor instead of using `add_handler()`, ensuring proper separation is maintained. ## Issue Fixes #32028 ## Dependencies None ## Testing - Modified existing test `test_merge_preserves_handler_distinction()` to verify handlers remain properly separated after merge ## Checklist - [x] **Breaking Changes**: No breaking changes - only fixes incorrect behavior - [x] **Type Hints**: All functions have complete type annotations - [x] **Tests**: Fix is fully tested with existing unit test - [x] **Security**: No security implications - [x] **Documentation**: No documentation changes needed - bug fix only - [x] **Code Quality**: Passes lint and format checks - [x] **Commit Message**: Follows Conventional Commits format --------- Co-authored-by: Mason Daugherty <mason@langchain.dev>
Packages
Important
This repository is structured as a monorepo, with various packages located in this libs/ directory. Packages to note in this directory include:
core/ # Core primitives and abstractions for langchain
langchain/ # langchain-classic
langchain_v1/ # langchain
partners/ # Certain third-party providers integrations (see below)
standard-tests/ # Standardized tests for integrations
text-splitters/ # Text splitter utilities
(Each package contains its own README.md file with specific details about that package.)
Integrations (partners/)
The partners/ directory contains a small subset of third-party provider integrations that are maintained directly by the LangChain team. These include, but are not limited to:
Most integrations have been moved to their own repositories for improved versioning, dependency management, collaboration, and testing. This includes packages from popular providers such as Google and AWS. Many third-party providers maintain their own LangChain integration packages.
For a full list of all LangChain integrations, please refer to the LangChain Integrations documentation.