78a3cbcc6b
The [Fireworks release job](https://github.com/langchain-ai/langchain/actions/runs/36479033898/job/109120052547) failed 55 tests because `kimi-k2p6` returned `404 NOT_FOUND`; the `gpt-oss-120b` chat tests passed in that same job. - Use `accounts/fireworks/models/gpt-oss-120b` across the affected chat, completions, and standard integration tests, reusing the existing chat-model constant. - Preserve all assertions and coverage; leave production defaults and release workflows unchanged. - Fireworks [advertises GPT-OSS-120B as serverless](https://fireworks.ai/models/fireworks/gpt-oss-120b). Live completions and expanded chat coverage still need confirmation with CI credentials: no Fireworks API key is available locally. This is not evidence that Kimi was retired. Made by [Open SWE](https://github.com/langchain-ai/open-swe) · [view thread](https://openswe.langchain.dev/agents/b8a0feec-8262-501b-8d6f-204f467461e3) · openai:gpt-6-astra (medium) Co-authored-by: Mason Daugherty <mdrxy@users.noreply.github.com> Co-authored-by: open-swe[bot] <open-swe@users.noreply.github.com>
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
model-profiles/ # Model capability profiles and CLI (`langchain-model-profiles`)
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.