langchain-dependencies

Key principles: Both sit on top of langchain + langchain-core + langsmith . These packages have tighter compatibility requirements — use the latest available version unless you have a specific reason not to. langchain-community stability note: This package is NOT on semantic versioning. Minor releases can contain breaking changes. Prefer dedicated integration packages (e.g. langchain-chroma , langchain-tavily ) when they exist — they are independently versioned and more stable. @langchain/core must be installed explicitly in yarn workspaces and monorepos — it is a peer dependency and will not always be hoisted automatically. langchain-tavily # use latest; partner package, semver langchain-chroma # use latest; partner package, semver langchain-text-splitters # use latest; semver Breaking changes only happen in major versions (1.x → 2.x) for all semver-compliant packages. Deprecated features remain functional across the entire 1.x series with warnings. Prefer dedicated integration packages over langchain-community. When a dedicated package exists (e.g. langchain-chroma instead of langchain-community 's Chroma integration), use it — dedicated packages are independently versioned and better tested.