4360 Commits (e1d113ea84a2edcf4a7709fc5be0e972ea74a5d9)

Author	SHA1	Message	Date
Bagatur	e1d113ea84	core,openai,grow,fw[patch]: deprecate bind_functions, update chat mod… (#26584) ... …el api ref	5 days ago
ccurme	6758894af1	docs: update v0.3 integrations table (#26571)	5 days ago
venkatram-dev	6ba3c715b7	doc_fix_chroma_integration (#26565) ... Thank you for contributing to LangChain! - [x] **PR title**: "package: description" docs:integrations:vectorstores:chroma:fix_typo - [x] **PR message**: ***Delete this entire checklist*** and replace with - **Description:** fix_typo in docs:integrations:vectorstores:chroma https://python.langchain.com/docs/integrations/vectorstores/chroma/ - **Issue:** https://github.com/langchain-ai/langchain/issues/26561 - [ ] **Add tests and docs**: If you're adding a new integration, please include 1. a test for the integration, preferably unit tests that do not rely on network access, 2. an example notebook showing its use. It lives in `docs/docs/integrations` directory. - [ ] **Lint and test**: Run `make format`, `make lint` and `make test` from the root of the package(s) you've modified. See contribution guidelines for more: https://python.langchain.com/docs/contributing/ Additional guidelines: - Make sure optional dependencies are imported within a function. - Please do not add dependencies to pyproject.toml files (even optional ones) unless they are required for unit tests. - Most PRs should not touch more than one package. - Changes should be backwards compatible. - If you are adding something to community, do not re-import it in langchain. If no one reviews your PR within a few days, please @-mention one of baskaryan, efriis, eyurtsev, ccurme, vbarda, hwchase17.	5 days ago
Bagatur	31f61d4d7d	docs: v0.3 nits (#26556)	6 days ago
Bagatur	99abd254fb	docs: clean up init_chat_model (#26551)	6 days ago
Bagatur	0bd98c99b3	docs: add sema4 to release table (#26549)	6 days ago
Eugene Yurtsev	8a2f2fc30b	docs: what langchain-cli migrate can do (#26547)	6 days ago
SQpgducray	724a53711b	docs: Fix missing `self` argument in `_get_docs_with_query` method of `Cust… (#26312) ... …omSelfQueryRetriever` This commit corrects an issue in the `_get_docs_with_query` method of the `CustomSelfQueryRetriever` class. The method was incorrectly using `self.vectorstore.similarity_search_with_score(query, **search_kwargs)` without including the `self` argument, which is required for proper method invocation. The `self` argument is necessary for calling instance methods and accessing instance attributes. By including `self` in the method call, we ensure that the method is correctly executed in the context of the current instance, allowing it to function as intended. No other changes were made to the method's logic or functionality. Thank you for contributing to LangChain! - [ ] **PR title**: "package: description" - Where "package" is whichever of langchain, community, core, experimental, etc. is being modified. Use "docs: ..." for purely docs changes, "templates: ..." for template changes, "infra: ..." for CI changes. - Example: "community: add foobar LLM" - [ ] **PR message**: ***Delete this entire checklist*** and replace with - **Description:** a description of the change - **Issue:** the issue # it fixes, if applicable - **Dependencies:** any dependencies required for this change - **Twitter handle:** if your PR gets announced, and you'd like a mention, we'll gladly shout you out! - [ ] **Add tests and docs**: If you're adding a new integration, please include 1. a test for the integration, preferably unit tests that do not rely on network access, 2. an example notebook showing its use. It lives in `docs/docs/integrations` directory. - [ ] **Lint and test**: Run `make format`, `make lint` and `make test` from the root of the package(s) you've modified. See contribution guidelines for more: https://python.langchain.com/docs/contributing/ Additional guidelines: - Make sure optional dependencies are imported within a function. - Please do not add dependencies to pyproject.toml files (even optional ones) unless they are required for unit tests. - Most PRs should not touch more than one package. - Changes should be backwards compatible. - If you are adding something to community, do not re-import it in langchain. If no one reviews your PR within a few days, please @-mention one of baskaryan, efriis, eyurtsev, ccurme, vbarda, hwchase17. Co-authored-by: Erick Friis <erick@langchain.dev>	6 days ago
Eugene Yurtsev	c6a78132d6	docs: show how to use langchain-cli for migration (#26535) ... Update v0.3 instructions a bit --------- Co-authored-by: Bagatur <22008038+baskaryan@users.noreply.github.com>	6 days ago
Bagatur	a319a0ff1d	docs: add redirects for tools and lcel (#26541)	6 days ago
ccurme	0154c586d3	docs: update integrations table in 0.3 guide (#26536)	6 days ago
Yoshitaka Fujii	bd42344b0a	docs: Update concepts.mdx (#26496) ... - Fix comments in Python - Fix repeated sentences	7 days ago
Erick Friis	9f5960a0aa	docs: new algolia index (#26508)	7 days ago
Erick Friis	135afdf4fb	docs: most 0.1 redirects too (#26494) ... takes redirects from 0.1 docs and factors them into suggested redirects in 0.3 docs	1 week ago
Bhadresh Savani	f66b7ba32d	Update google_search.ipynb (#26420) ... Added changes for pip installation	1 week ago
Nicolas	2240ca2979	docs: Fix Firecrawl v0 version (#26452) ... Firecrawl integration is currently on v0 - which is supported until version 0.0.20. @rafaelsideguide is working on a pr for v1 but meanwhile we should fix the docs.	1 week ago
Bagatur	b47f4cfe51	mongodb[minor]: Release 0.2.0 (#26484)	1 week ago
Bagatur	779a008d4e	docs: update v3 versions (#26483)	1 week ago
Bagatur	fa8e0d90de	docs: update version docs (#26457)	1 week ago
Erick Friis	c2a3021bb0	multiple: pydantic 2 compatibility, v0.3 (#26443) ... Signed-off-by: ChengZi <chen.zhang@zilliz.com> Co-authored-by: Eugene Yurtsev <eyurtsev@gmail.com> Co-authored-by: Bagatur <22008038+baskaryan@users.noreply.github.com> Co-authored-by: Dan O'Donovan <dan.odonovan@gmail.com> Co-authored-by: Tom Daniel Grande <tomdgrande@gmail.com> Co-authored-by: Grande <Tom.Daniel.Grande@statsbygg.no> Co-authored-by: Bagatur <baskaryan@gmail.com> Co-authored-by: ccurme <chester.curme@gmail.com> Co-authored-by: Harrison Chase <hw.chase.17@gmail.com> Co-authored-by: Tomaz Bratanic <bratanic.tomaz@gmail.com> Co-authored-by: ZhangShenao <15201440436@163.com> Co-authored-by: Friso H. Kingma <fhkingma@gmail.com> Co-authored-by: ChengZi <chen.zhang@zilliz.com> Co-authored-by: Nuno Campos <nuno@langchain.dev> Co-authored-by: Morgante Pell <morgantep@google.com>	1 week ago
jessicaou	396c0aee4d	docs: Adding LC Academy links (#26164) ... Thank you for contributing to LangChain! - [ ] **PR title**: "package: description" - Where "package" is whichever of langchain, community, core, experimental, etc. is being modified. Use "docs: ..." for purely docs changes, "templates: ..." for template changes, "infra: ..." for CI changes. - Example: "community: add foobar LLM" - [ ] **PR message**: ***Delete this entire checklist*** and replace with - **Description:** a description of the change - **Issue:** the issue # it fixes, if applicable - **Dependencies:** any dependencies required for this change - **Twitter handle:** if your PR gets announced, and you'd like a mention, we'll gladly shout you out! - [ ] **Add tests and docs**: If you're adding a new integration, please include 1. a test for the integration, preferably unit tests that do not rely on network access, 2. an example notebook showing its use. It lives in `docs/docs/integrations` directory. - [ ] **Lint and test**: Run `make format`, `make lint` and `make test` from the root of the package(s) you've modified. See contribution guidelines for more: https://python.langchain.com/docs/contributing/ Additional guidelines: - Make sure optional dependencies are imported within a function. - Please do not add dependencies to pyproject.toml files (even optional ones) unless they are required for unit tests. - Most PRs should not touch more than one package. - Changes should be backwards compatible. - If you are adding something to community, do not re-import it in langchain. If no one reviews your PR within a few days, please @-mention one of baskaryan, efriis, eyurtsev, ccurme, vbarda, hwchase17. --------- Co-authored-by: Jess Ou <jessou@jesss-mbp.local.meter> Co-authored-by: Erick Friis <erick@langchain.dev>	2 weeks ago
William FH	d87feb1b04	[Docs] Correct the admonition explaining min langchain-anthropic version in doc (#26359) ... 0.1.15 instead of just 0.1.5	2 weeks ago
Emad Rad	16d41eab1e	docs: typos fixed (#26234) ... While going through the chatbot tutorial, I noticed a couple of typos and grammatical issues. Also, the pip install command for langchain_community was commented out, but the document mentions installing it. --------- Co-authored-by: Erick Friis <erickfriis@gmail.com>	2 weeks ago
venkatram-dev	fa229d6c02	docs: fix_typo_llm_chain_tutorial (#26229) ... Thank you for contributing to LangChain! - [ ] **PR title**: "package: description" docs:tutorials:llm_chain:fix typo - [ ] **PR message**: fix typo in llm chain tutorial - [ ] **Add tests and docs**: If you're adding a new integration, please include 1. a test for the integration, preferably unit tests that do not rely on network access, 2. an example notebook showing its use. It lives in `docs/docs/integrations` directory. - [ ] **Lint and test**: Run `make format`, `make lint` and `make test` from the root of the package(s) you've modified. See contribution guidelines for more: https://python.langchain.com/docs/contributing/ Additional guidelines: - Make sure optional dependencies are imported within a function. - Please do not add dependencies to pyproject.toml files (even optional ones) unless they are required for unit tests. - Most PRs should not touch more than one package. - Changes should be backwards compatible. - If you are adding something to community, do not re-import it in langchain. If no one reviews your PR within a few days, please @-mention one of baskaryan, efriis, eyurtsev, ccurme, vbarda, hwchase17. Co-authored-by: Erick Friis <erick@langchain.dev>	2 weeks ago
miri-bar	3e48c728d5	docs: add ai21 tool calling example (#26199) ... Add tool calling example to AI21 docs	2 weeks ago
Geoffrey HARRAZI	76bce42629	docs: Update Google BigQuery Vector Search with new SQL filter feature introduce in langchain-google-community 1.0.9 (#26184) ... Hello, fix: https://github.com/langchain-ai/langchain/issues/26183 Adding documentation regarding SQL like filter for Google BigQuery Vector Search coming in next langchain-google-community 1.0.9 release. Note: langchain-google-community==1.0.9 is not yet released Question: There is no way to warn the user int the doc about the availability of a feature after a specific package version ? --------- Co-authored-by: Erick Friis <erick@langchain.dev>	2 weeks ago
Matt Hull	bca51ca164	docs: Update func doc strings in tools_human (#26149) ... Thank you for contributing to LangChain! - [x] **PR title**: "package: description" - Where "package" is whichever of langchain, community, core, experimental, etc. is being modified. Use "docs: ..." for purely docs changes, "templates: ..." for template changes, "infra: ..." for CI changes. - Example: "community: add foobar LLM" - [x] **PR message**: ***Delete this entire checklist*** and replace with - **Description:** Fix docstring for two functions that look like have docstrings carried over from other functions. - **Issue:** Not found issue reporting the miss-leading docstrings. - **Dependencies:** None - **Twitter handle:** - [x] **Add tests and docs**: If you're adding a new integration, please include 1. a test for the integration, preferably unit tests that do not rely on network access, 2. an example notebook showing its use. It lives in `docs/docs/integrations` directory. - [x] **Lint and test**: Run `make format`, `make lint` and `make test` from the root of the package(s) you've modified. See contribution guidelines for more: https://python.langchain.com/docs/contributing/ Additional guidelines: - Make sure optional dependencies are imported within a function. - Please do not add dependencies to pyproject.toml files (even optional ones) unless they are required for unit tests. - Most PRs should not touch more than one package. - Changes should be backwards compatible. - If you are adding something to community, do not re-import it in langchain. If no one reviews your PR within a few days, please @-mention one of baskaryan, efriis, eyurtsev, ccurme, vbarda, hwchase17. --------- Co-authored-by: Erick Friis <erick@langchain.dev>	2 weeks ago
Qasim Khan	fa17b145bb	docs: fix typo in graph_constructing tutorial (#26134) ... Changed > "At a high-level, the steps of constructing a knowledge are from text are:" to > "At a high-level, the steps of constructing a knowledge graph from text are:" Co-authored-by: Erick Friis <erick@langchain.dev>	2 weeks ago
Malik Ashar Khan	042e84170b	Fix typo in ScrapflyLoader documentation (#26117) ... This PR fixes a minor typo in the ScrapflyLoader documentation. The word "passigng" was changed to "passing." Before: passigng After: passing This change improves the clarity and professionalism of the documentation. Co-authored-by: Ashar <asharmalik.ds193@gmail.com>	2 weeks ago
Leonid Ganeline	2f80d67dc1	docs: `integrations` reference updates 16 (#26059) ... Added missed provider pages and links. Fixed inconsistent formatting. Co-authored-by: Erick Friis <erick@langchain.dev>	2 weeks ago
Ikko Eltociear Ashimine	ffdc370200	docs: update agent_executor.ipynb (#26035) ... initalize -> initialize Co-authored-by: Erick Friis <erick@langchain.dev>	2 weeks ago
Leonid Ganeline	5052e87d7c	docs: `integrations` reference updates 15 (#25994) ... Added missed provider pages and links. Fixed inconsistent formatting.	2 weeks ago
Brace Sproul	854f37be87	docs[minor]: Add state of agents survey to docs announcement bar (#26167)	2 weeks ago
Yuki Watanabe	ef329f6819	docs: Fix databricks doc (#25941) ... https://github.com/langchain-ai/langchain/pull/25929 broke the layout because of missing `:::` for the caution clause. Signed-off-by: B-Step62 <yuki.watanabe@databricks.com>	3 weeks ago
Bagatur	f872c50b3f	docs: installation nits (#24484)	3 weeks ago
JonZeolla	78ff51ce83	community[patch]: update the default hf bge embeddings (#22627) ... **Description:** This updates the langchain_community > huggingface > default bge embeddings ([the current default recommends this change](https://huggingface.co/BAAI/bge-large-en)) **Issue:** None **Dependencies:** None **Twitter handle:** @jonzeolla --------- Co-authored-by: Bagatur <baskaryan@gmail.com>	3 weeks ago
Leonid Ganeline	150251fd49	docs: `integrations` reference updates 13 (#25711) ... Added missed provider pages and links. Fixed inconsistent formatting. Added arxiv references to docstirngs. --------- Co-authored-by: Harrison Chase <hw.chase.17@gmail.com> Co-authored-by: Bagatur <22008038+baskaryan@users.noreply.github.com>	3 weeks ago
Yuki Watanabe	64dfdaa924	docs: Add Databricks integration (#25929) ... Updating the gateway pages in the documentation to name the `langchain-databricks` integration. --------- Signed-off-by: B-Step62 <yuki.watanabe@databricks.com> Co-authored-by: Bagatur <baskaryan@gmail.com>	3 weeks ago
Yash Parmar	51dae57357	community[minor]: jina search tools integrating (jina reader) (#23339) ... - **PR title**: "community: add Jina Search tool" - **Description:** Added the Jina Search tool for querying the Jina search API. This includes the implementation of the JinaSearchAPIWrapper and the JinaSearch tool, along with a Jupyter notebook example demonstrating its usage. - **Issue:** N/A - **Dependencies:** N/A - **Twitter handle:** [Twitter handle](https://x.com/yashp3020?t=7wM0gQ7XjGciFoh9xaBtqA&s=09) - [x] **Add tests and docs**: If you're adding a new integration, please include 1. an example notebook showing its use. It lives in `docs/docs/integrations` directory. - [ ] **Lint and test**: Run `make format`, `make lint` and `make test` from the root of the package(s) you've modified. See contribution guidelines for more: https://python.langchain.com/docs/contributing/ --------- Co-authored-by: Bagatur <baskaryan@gmail.com> Co-authored-by: Chester Curme <chester.curme@gmail.com>	3 weeks ago
venkatram-dev	a09e2afee4	typo_summarization_tutorial (#25938) ... Thank you for contributing to LangChain! - [ ] **PR title**: docs: fix typo in summarization_tutorial - [ ] **PR message**: docs: fix couple of typos in summarization_tutorial - [ ] **Add tests and docs**: If you're adding a new integration, please include 1. a test for the integration, preferably unit tests that do not rely on network access, 2. an example notebook showing its use. It lives in `docs/docs/integrations` directory. - [ ] **Lint and test**: Run `make format`, `make lint` and `make test` from the root of the package(s) you've modified. See contribution guidelines for more: https://python.langchain.com/docs/contributing/ Additional guidelines: - Make sure optional dependencies are imported within a function. - Please do not add dependencies to pyproject.toml files (even optional ones) unless they are required for unit tests. - Most PRs should not touch more than one package. - Changes should be backwards compatible. - If you are adding something to community, do not re-import it in langchain. If no one reviews your PR within a few days, please @-mention one of baskaryan, efriis, eyurtsev, ccurme, vbarda, hwchase17.	3 weeks ago
Jacob Lee	f49cce739b	👥 Update LangChain people data (#25917) ... 👥 Update LangChain people data Co-authored-by: github-actions <github-actions@github.com>	3 weeks ago
Leonid Ganeline	96b99a5022	docs: `integrations google` missed references (#25923) ... Added missed integration links. Fixed inconsistent formatting.	3 weeks ago
Leonid Ganeline	086556d466	docs: `integrations` reference updates 14 (#25928) ... Added missed provider pages and links. Fixed inconsistent formatting.	3 weeks ago
Tyler Wray	1ff8c36aa6	docs: fix pgvector link (#25930) ... - **Description:** pg_vector link is 404'ing. This fixes it.	3 weeks ago
Yuwen Hu	566e9ba164	community: add Intel GPU support to `ipex-llm` llm integration (#22458) ... **Description:** [IPEX-LLM](https://github.com/intel-analytics/ipex-llm) is a PyTorch library for running LLM on Intel CPU and GPU (e.g., local PC with iGPU, discrete GPU such as Arc, Flex and Max) with very low latency. This PR adds Intel GPU support to `ipex-llm` llm integration. **Dependencies:** `ipex-llm` **Contribution maintainer**: @ivy-lv11 @Oscilloscope98 **tests and docs**: - Add: langchain/docs/docs/integrations/llms/ipex_llm_gpu.ipynb - Update: langchain/docs/docs/integrations/llms/ipex_llm_gpu.ipynb - Update: langchain/libs/community/tests/llms/test_ipex_llm.py --------- Co-authored-by: ivy-lv11 <zhicunlv@gmail.com>	3 weeks ago
Kirushikesh DB	7f857a02d5	docs: HuggingFace pipeline returns the prompt if return_full_text is not set (#25916) ... Thank you for contributing to LangChain! **Description:** The current documentation of using the Huggingface with Langchain needs to set return_full_text as False otherwise pipeline by default returns both the prompt and response as output. Code to reproduce: ```python from langchain_huggingface import ChatHuggingFace, HuggingFacePipeline from langchain_core.messages import ( HumanMessage, SystemMessage, ) llm = HuggingFacePipeline.from_model_id( model_id="microsoft/Phi-3.5-mini-instruct", task="text-generation", pipeline_kwargs=dict( max_new_tokens=512, do_sample=False, repetition_penalty=1.03, # return_full_text=False ), device=0 ) chat_model = ChatHuggingFace(llm=llm) messages = [ SystemMessage(content="You're a helpful assistant"), HumanMessage( content="What happens when an unstoppable force meets an immovable object?" ), ] ai_msg = chat_model.invoke(messages) print(ai_msg.content) ``` Output: ``` <|system|> You're a helpful assistant<|end|> <|user|> What happens when an unstoppable force meets an immovable object?<|end|> <|assistant|> The scenario of an "unstoppable force" meeting an "immovable object" is a classic paradox that has puzzled philosophers, scientists, and thinkers for centuries. In physics, however, there are no such things as truly unstoppable forces or immovable objects because all physical entities have mass and interact with other masses through fundamental forces (like gravity). When we consider the laws of motion, particularly Newton's third law which states that for every action, there is an equal and opposite reaction, it becomes clear that if one were to exist, the other would necessarily be negated by the interaction. For example, if you push against a solid wall with great force, the wall exerts an equal and opposite force back on you, preventing your movement. In theoretical discussions, this paradox often serves as a thought experiment to explore concepts like determinism versus free will, the limits of physical laws, and the nature of reality itself. However, in practical terms, any force applied to an object will result in some form of deformation, transfer of energy, or movement, depending on the properties of both the force and the object. So while the idea of an unstoppable force and an immovable object remains a fascinating philosophical conundrum, it does not hold up under the scrutiny of physical laws as we understand them. ``` --------- Co-authored-by: Kirushikesh D B kirushi@ibm.com <kirushi@cccxl012.pok.ibm.com>	3 weeks ago
Borahm Lee	9cdb99bd60	docs: remove unused imports in Tutorials Basics (#25919) ... ## Description - `List` is not explicitly used, so the unnecessary imports will be removed.	3 weeks ago
Erick Friis	8732cfc6ef	docs: review process gh discussion (#25921)	3 weeks ago
Erick Friis	08b9715845	docs: pr review process (#25899) ... Co-authored-by: Bagatur <22008038+baskaryan@users.noreply.github.com>	3 weeks ago
Sandeep Bhandari	f882824eac	Update tool_choice.ipynb spelling mistake of select (#25907) ... Thank you for contributing to LangChain! - [ ] **PR title**: "package: description" - Where "package" is whichever of langchain, community, core, experimental, etc. is being modified. Use "docs: ..." for purely docs changes, "templates: ..." for template changes, "infra: ..." for CI changes. - Example: "community: add foobar LLM" - [ ] **PR message**: ***Delete this entire checklist*** and replace with - **Description:** a description of the change - **Issue:** the issue # it fixes, if applicable - **Dependencies:** any dependencies required for this change - **Twitter handle:** if your PR gets announced, and you'd like a mention, we'll gladly shout you out! - [ ] **Add tests and docs**: If you're adding a new integration, please include 1. a test for the integration, preferably unit tests that do not rely on network access, 2. an example notebook showing its use. It lives in `docs/docs/integrations` directory. - [ ] **Lint and test**: Run `make format`, `make lint` and `make test` from the root of the package(s) you've modified. See contribution guidelines for more: https://python.langchain.com/docs/contributing/ Additional guidelines: - Make sure optional dependencies are imported within a function. - Please do not add dependencies to pyproject.toml files (even optional ones) unless they are required for unit tests. - Most PRs should not touch more than one package. - Changes should be backwards compatible. - If you are adding something to community, do not re-import it in langchain. If no one reviews your PR within a few days, please @-mention one of baskaryan, efriis, eyurtsev, ccurme, vbarda, hwchase17.	3 weeks ago