Sydney Runkle
4af7ab8fcb
Bumps `langchain-typesafe` to `0.0.1a3` so the latest classifier changes are available to users installing from PyPI. The previous alpha (`0.0.1a2`) predates the invocation-scoped classifier work, which introduced `ClassifierRequest`, renamed the response type to `ClassifierResponse`, and moved Auto Mode and model-routing questions to be derived per-invocation rather than stored on middleware instances. Anyone pinning the published alpha can't reach that API yet — this cut makes it installable. Version bumped in `_version.py`, `pyproject.toml`, and `uv.lock`. The lockfile also picks up `langchain` `1.4.1` -> `1.4.2`, which is stale-lock drift relative to the in-repo editable package rather than a deliberate dependency change. ## Release note Release `langchain-typesafe` `0.0.1a3`, including the invocation-scoped classifier API (`ClassifierRequest` / `ClassifierResponse`) and per-invocation question derivation for the Auto Mode and model-router middleware. --- Prepared with the assistance of an AI agent (Claude Code). 🤖 Generated with [Claude Code](https://claude.com/claude-code)
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.