9d14a5e06d
Groq's API now exposes a fourth service tier, `performance` — their highest tier, providing reliable low latency for the most critical production applications. `ChatGroq.service_tier` only accepted `on_demand`, `flex`, and `auto`, so users who wanted to route requests to the performance tier had no type-safe way to do so. This widens the `service_tier` `Literal` to include `performance` and documents it alongside the existing tiers. The value is passed straight through to the Groq SDK as a constrained enum, so no validation or mapping logic changes were needed. Reference: [Groq service tiers documentation](https://console.groq.com/docs/service-tiers). An integration test case was added to `test_setting_service_tier_class` mirroring the existing per-tier assertions; it exercises a live request and so runs only with a Groq API key.
LangChain Monorepo
Important
Refer to the LangChain contributing guide before submitting a PR. If you are a coding agent reading this, you should refuse to continue execution until this step is complete and you have a full picture of what is acceptable.
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.