11 Commits (bd3e7d50f332f01488774cbe8bc30bfd55d6e70c)

Author	SHA1	Message	Date
Erick Friis	aca98fd150	multiple: releases with relaxed core dep (#21724)	4 months ago
Erick Friis	c77d2f2b06	multiple: core 0.2 nonbreaking dep, check_diff community->langchain dep (#21646) ... 0.2 is not a breaking release for core (but it is for langchain and community) To keep the core+langchain+community packages in sync at 0.2, we will relax deps throughout the ecosystem to tolerate `langchain-core` 0.2	4 months ago
Charlie Marsh	fd94aa8366	partner[patch]: Upgrade to Ruff v0.4.2 (#21108) ... ## Summary No new diagnostics (given that the set of enabled rules hasn't changed), but gains access to our new parser (much faster) and reduced false positives all around.	5 months ago
Erick Friis	391e8f2050	pinecone[patch]: fix core min version (#20177)	6 months ago
Erick Friis	96dc0ea49d	pinecone[patch]: release 0.1.0 (#20109)	6 months ago
Erick Friis	d5a2ff58e9	pinecone[patch]: source tag (#19739)	6 months ago
Erick Friis	a53370a060	pinecone[patch], docs: PineconeVectorStore, release 0.0.3 (#17896)	7 months ago
Erick Friis	9eb1b56e73	pinecone[patch]: release 0.0.2 (#17477)	7 months ago
Erick Friis	10bdf2422c	pinecone[patch]: release 0.0.2rc0, remove simsimd dep (#17469)	7 months ago
Erick Friis	99540d3d75	infra: no print in newer partner packages (#17353) ... <!-- Thank you for contributing to LangChain! Please title your PR "<package>: <description>", where <package> is whichever of langchain, community, core, experimental, etc. is being modified. Replace this entire comment with: - **Description:** a description of the change, - **Issue:** the issue # it fixes if applicable, - **Dependencies:** any dependencies required for this change, - **Twitter handle:** we announce bigger features on Twitter. If your PR gets announced, and you'd like a mention, we'll gladly shout you out! Please make sure your PR is passing linting and testing before submitting. Run `make format`, `make lint` and `make test` from the root of the package you've modified to check this locally. See contribution guidelines for more information on how to write/run tests, lint, etc: https://python.langchain.com/docs/contributing/ 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. If no one reviews your PR within a few days, please @-mention one of @baskaryan, @eyurtsev, @hwchase17. -->	8 months ago
Erick Friis	6ffd5b15bc	pinecone: init pkg (#16556) ... <!-- Thank you for contributing to LangChain! Please title your PR "<package>: <description>", where <package> is whichever of langchain, community, core, experimental, etc. is being modified. Replace this entire comment with: - **Description:** a description of the change, - **Issue:** the issue # it fixes if applicable, - **Dependencies:** any dependencies required for this change, - **Twitter handle:** we announce bigger features on Twitter. If your PR gets announced, and you'd like a mention, we'll gladly shout you out! Please make sure your PR is passing linting and testing before submitting. Run `make format`, `make lint` and `make test` from the root of the package you've modified to check this locally. See contribution guidelines for more information on how to write/run tests, lint, etc: https://python.langchain.com/docs/contributing/ 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. If no one reviews your PR within a few days, please @-mention one of @baskaryan, @eyurtsev, @hwchase17. -->	8 months ago