build(deps): bump @langchain/core from 0.3.62 to 1.1.8#675
build(deps): bump @langchain/core from 0.3.62 to 1.1.8#675dependabot[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 |
a523148 to
994dff2
Compare
994dff2 to
bf8d686
Compare
Bumps [@langchain/core](https://github.com/langchain-ai/langchainjs) from 0.3.62 to 1.1.8. - [Release notes](https://github.com/langchain-ai/langchainjs/releases) - [Commits](https://github.com/langchain-ai/langchainjs/compare/@langchain/core==0.3.62...@langchain/core@1.1.8) --- updated-dependencies: - dependency-name: "@langchain/core" dependency-version: 1.1.8 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
bf8d686 to
1e7b08c
Compare
JiwaniZakir
left a comment
There was a problem hiding this comment.
This is a major version bump (0.x → 1.x) for @langchain/core, not a minor dependency update — @langchain/core 1.0 introduced breaking changes to several core abstractions including message serialization, tool calling interfaces, and the Runnable API. The PR title claims the bump is "from 0.3.62 to 1.1.8," but the actual diff shows ^0.3.80 → ^1.1.17, which is a discrepancy worth noting. Given that packages/core directly depends on this and adapter packages like adapter-claude, adapter-openai, and adapter-gemini all build on top of it, any changed method signatures or removed exports in @langchain/core 1.x (e.g., changes to BaseMessage, BaseChatModel, or tool schema types) could silently break at runtime even if the build passes. It would be worth confirming that the source files in each adapter package — particularly around message construction and tool definitions — have been audited against the @langchain/core 1.x migration guide, and that integration tests cover at least one full request/response cycle per adapter.
Bumps @langchain/core from 0.3.62 to 1.1.8.
Release notes
Sourced from
@langchain/core's releases.... (truncated)
Commits
de32b32chore: version packages (#9697)e5063f9fix!(core/langchain): hardening forload(#9707)8b3e611chore(turbopuffer): rollback version (#9698)8996647fix(core): document purpose of name in base message (#9684)8df6264chore: version packages (#9676)df9c42bfeat(core): usage_metadata in extra.metadata (#9686)4ea3a52fix(ci): use appropriate path for core PR labels (#9696)ffb2402feat(langchain):context(#9673)8d2982bfeat(core): Make runnable transform trace in a single payload in LangChainTra...2b36431fix(mcp-adapters): bump@modelcontextprotocol/sdkto address CVE-2025-66414 (...Maintainer changes
This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for
@langchain/coresince 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)