fix: langchain version

[akitaSummer]

Checklist

• npm test passes
• tests and/or benchmarks are included
• documentation is changed or added
• commit message follows commit guidelines

Affected core subsystem(s)

Description of change

Summary by CodeRabbit

• Chores
  • Updated LangChain dependencies to use semantic versioning ranges in core framework and plugin modules.
  • Version constraints now permit compatible minor and patch updates to be resolved automatically.
  • No changes to application code, APIs, or functionality.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

Two package.json files were updated to relax LangChain dependency version constraints. Dependencies @langchain/core, @langchain/langgraph, and langchain were changed from exact version pins to caret ranges, allowing compatible minor and patch updates while maintaining stability.

Changes

Cohort / File(s)	Summary
LangChain Dependency Version Relaxation core/langchain-decorator/package.json, plugin/langchain/package.json	Three dependencies updated from exact pins to caret ranges: @langchain/core (1.1.1 → ^1.1.1), @langchain/langgraph (1.0.2 → ^1.0.2), langchain (1.1.2 → ^1.1.2). Enables automatic minor/patch updates while preventing breaking changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• feat: use langchain for deepagents #376: Performs inverse operation by pinning the same caret-versioned dependencies to exact versions in the same package.json files.

Suggested reviewers

• killagu

Poem

🐰 Hop along with versions free,
Caret ranges let packages be,
Minor patches hop their way,
Flexibility wins the day! 🌱

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'fix: langchain version' is vague and does not clearly communicate the specific change made. It does not specify what aspect of the langchain version was fixed or why the dependency ranges were relaxed from exact pins to caret ranges.	Consider using a more descriptive title such as 'chore: relax langchain dependencies to caret ranges' or 'chore: allow minor updates for langchain packages' to clearly convey the nature of the dependency version change.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/langchain-version

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Summary of Changes

Hello @akitaSummer, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request modifies the dependency declarations for several Langchain-related packages within the project's package.json files. By switching from exact version pinning to caret ranges, the project will now automatically accept minor and patch updates for these dependencies, enhancing maintainability and ensuring the use of the latest non-breaking features and fixes without requiring manual version bumps.

Highlights

• Dependency Versioning: Updated Langchain-related package dependencies (@langchain/core, @langchain/langgraph, langchain) from exact versions to caret ranges in package.json files.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates several langchain dependencies in core/langchain-decorator/package.json and plugin/langchain/package.json to use caret version ranges (^) instead of pinned versions. This is a positive change that allows for more flexible dependency management and aligns with the versioning strategy of other packages.

My review includes feedback on improving dependency consistency across the monorepo. Specifically, I've pointed out that some @langchain package versions are out of sync between the two modified package.json files. I've also identified a critical issue in core/langchain-decorator/package.json where the declared engines.node version is incompatible with the requirements of the langchain dependency. Addressing these points will improve the stability and correctness of these packages.

[coderabbitai]

Actionable comments posted: 2

📜 Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6a262fa and 5958ec4.

📒 Files selected for processing (2)

• core/langchain-decorator/package.json
• plugin/langchain/package.json

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (6)

• GitHub Check: Runner-ubuntu (18)
• GitHub Check: Runner-ubuntu (16)
• GitHub Check: Runner-macos (20)
• GitHub Check: Runner-macos (18)
• GitHub Check: Runner-macos (16)
• GitHub Check: Runner-ubuntu (20)

[killagu]

LGTM