build(deps): bump @langchain/community from 0.3.48 to 1.1.1#677
build(deps): bump @langchain/community from 0.3.48 to 1.1.1#677dependabot[bot] wants to merge 1 commit intov1-devfrom
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the Comment |
Bumps [@langchain/community](https://github.com/langchain-ai/langchainjs) from 0.3.48 to 1.1.1. - [Release notes](https://github.com/langchain-ai/langchainjs/releases) - [Commits](https://github.com/langchain-ai/langchainjs/compare/@langchain/community==0.3.48...langchain@1.1.1) --- updated-dependencies: - dependency-name: "@langchain/community" dependency-version: 1.1.1 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
4b26a36 to
92a20c6
Compare
JiwaniZakir
left a comment
There was a problem hiding this comment.
This bump crosses a major version boundary (0.3.x → 1.1.1), which in @langchain/community typically carries breaking changes to vector store interfaces, embeddings APIs, and retriever contracts — worth verifying that none of the integrations used in packages/service-vector-store (Redis, luna-vdb, etc.) are affected. There's also a likely peer dependency conflict: @langchain/community 1.x generally requires @langchain/core 1.x, but package.json still pins @langchain/core to ^0.3.80, which could cause subtle runtime mismatches or install warnings depending on the package manager's resolution strategy. It would be worth checking whether @langchain/redis (^0.1.3) and @chatluna/luna-vdb (^0.0.12) have been validated against @langchain/community 1.x, since they may transitively depend on the same @langchain/core version range. Finally, there's no mention of a lockfile update or any integration tests being run against the new version — given the scope of this change, a note confirming CI passed end-to-end for the vector store package would strengthen confidence in the bump.
Bumps @langchain/community from 0.3.48 to 1.1.1.
Release notes
Sourced from
@langchain/community's releases.... (truncated)
Commits
862da50chore: version packages (#9489)cfee39achore(anthropic): bump sdk version (#9488)4827945fix(langchain): make core a workspace peer dep (#9487)426236echore(deps): bump actions/checkout from 5.0.1 to 6.0.0 in the major-deps-upda...88626fdchore(google-*): rollback to 1.0.4 (#9486)1596213Revert "Revert "chore: version packages (#9456)" (#9479)" (#9481)3c9ea66chore: fix links (#9483)9eb7346Revert "chore: version packages (#9456)" (#9479)5a3b3b9fix: workspace dependencies (#9478)32be443chore: version packages (#9456)Maintainer changes
This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for
@langchain/communitysince your current version.You can trigger a rebase of this PR by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)