Skip to content

[Snyk] Upgrade @langchain/core from 1.1.48 to 1.2.1 - #1046

Open
CMiville42 wants to merge 1 commit into
mainfrom
snyk-upgrade-52179f87634172154aad9043f41744e7
Open

[Snyk] Upgrade @langchain/core from 1.1.48 to 1.2.1#1046
CMiville42 wants to merge 1 commit into
mainfrom
snyk-upgrade-52179f87634172154aad9043f41744e7

Conversation

@CMiville42

Copy link
Copy Markdown

snyk-top-banner

Snyk has created this PR to upgrade @langchain/core from 1.1.48 to 1.2.1.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 8 versions ahead of your current version.

  • The recommended version was released a month ago.

Issues fixed by the recommended upgrade:

Issue Score Exploit Maturity
high severity Interpretation Conflict
SNYK-JS-FASTURI-18021349
49 No Known Exploit
high severity Directory Traversal
SNYK-JS-HONONODESERVER-18170326
49 No Known Exploit
high severity Deserialization of Untrusted Data
SNYK-JS-LANGSMITH-16658749
49 No Known Exploit
medium severity Improper Check for Unusual or Exceptional Conditions
SNYK-JS-PROTOBUFJSCODEGEN-16643292
49 No Known Exploit
medium severity Allocation of Resources Without Limits or Throttling
SNYK-JS-BODYPARSER-17906397
49 No Known Exploit
medium severity Prototype Pollution
SNYK-JS-LANGSMITH-15969264
49 Proof of Concept
medium severity Insertion of Sensitive Information into Log File
SNYK-JS-LANGSMITH-16082039
49 No Known Exploit

Breaking Change Risk

Merge Risk: Medium

Notice: This assessment is enhanced by AI.

Release notes
Package name: @langchain/core
  • 1.2.1 - 2026-06-22
  • 1.2.0 - 2026-06-17
  • 1.2.0-dev-1775763803878 - 2026-04-09
  • 1.2.0-dev-1765937705265 - 2025-12-17
  • 1.1.50-dev-1781580357424 - 2026-06-16
  • 1.1.49 - 2026-06-12
  • 1.1.49-dev-1781048185730 - 2026-06-09
  • 1.1.49-dev-1781044436312 - 2026-06-09
  • 1.1.48 - 2026-05-21
from @langchain/core GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

Snyk has created this PR to upgrade @langchain/core from 1.1.48 to 1.2.1.

See this package in npm:
@langchain/core

See this project in Snyk:
https://app.snyk.io/org/hedera-agent-kit/project/e00e6d1e-ba0f-49ee-afe5-97ee8cf7a032?utm_source=github&utm_medium=referral&page=upgrade-pr
@CMiville42

Copy link
Copy Markdown
Author

Merge Risk: Medium

This is a minor version upgrade. While no specific breaking API changes were found documented for @langchain/core in this version range, the risk is assessed as medium due to the nature of the LangChain ecosystem.

Key Considerations:

  • Dependency Synchronization: LangChain's official guidance states that for compatibility, all used LangChain packages (e.g., @langchain/openai, @langchain/community) must share the same version of @langchain/core.
  • Potential for Ripple Effects: Upgrading @langchain/core in isolation may cause compatibility issues with other @langchain/* packages in your project. You may need to upgrade other LangChain dependencies simultaneously, which could introduce breaking changes from those packages.

Recommendation:
Verify that all other @langchain/* packages in your project are compatible with @langchain/core@1.2.1 and upgrade them as needed. Test thoroughly after the upgrade to ensure the entire chain of dependencies functions as expected.

Source: Package documentation

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

@CMiville42
CMiville42 requested review from a team as code owners July 28, 2026 09:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants