Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Oct 18, 2025

This PR contains the following updates:

Package Change Age Confidence
@langchain/core (source) ^0.3.55^1.0.0 age confidence

Release Notes

langchain-ai/langchainjs (@​langchain/core)

v1.1.16

Compare Source

Patch Changes

v1.1.15

Patch Changes

v1.1.13

Compare Source

Patch Changes

v1.1.12

Compare Source

Patch Changes

v1.1.11

Compare Source

Patch Changes

v1.1.10

Compare Source

Patch Changes

v1.1.9

Compare Source

Patch Changes

v1.1.8

Patch Changes

v1.1.6

Compare Source

Patch Changes

v1.1.5

Compare Source

Patch Changes

v1.1.4

Compare Source

Patch Changes

v1.1.3

Compare Source

Patch Changes

v1.1.2

Compare Source

Patch Changes

v1.1.1

Patch Changes

v1.1.0

Minor Changes
Patch Changes

v1.0.6

Patch Changes

v1.0.5

Patch Changes

v1.0.4

Patch Changes

v1.0.3

Patch Changes

v1.0.2

Patch Changes

v1.0.1

Patch Changes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
Copy link
Contributor Author

renovate bot commented Oct 18, 2025

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @langchain/openai@0.6.17
npm error Found: @langchain/core@1.1.16
npm error node_modules/@langchain/core
npm error   @langchain/core@"^1.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @langchain/core@">=0.3.68 <0.4.0" from @langchain/openai@0.6.17
npm error node_modules/@langchain/openai
npm error   @langchain/openai@"^0.6.0" from the root project
npm error
npm error Conflicting peer dependency: @langchain/core@0.3.80
npm error node_modules/@langchain/core
npm error   peer @langchain/core@">=0.3.68 <0.4.0" from @langchain/openai@0.6.17
npm error   node_modules/@langchain/openai
npm error     @langchain/openai@"^0.6.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-01-21T00_54_47_761Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-01-21T00_54_47_761Z-debug-0.log

@yegor256
Copy link
Member

@rultor please, try to merge, since 16 checks have passed

@rultor
Copy link
Contributor

rultor commented Oct 18, 2025

@rultor please, try to merge, since 16 checks have passed

@yegor256 OK, I'll try to merge now. You can check the progress of the merge here.

@rultor
Copy link
Contributor

rultor commented Oct 18, 2025

@rultor please, try to merge, since 16 checks have passed

@renovate[bot] @yegor256 Oops, I failed. You can see the full log here (spent 2min).

npm warn EBADENGINE }
\u001b[1G\u001b[0K⠼\u001b[1G\u001b[0K⠴\u001b[1G\u001b[0K⠦\u001b[1G\u001b[0K⠧\u001b[1G\u001b[0K⠇\u001b[1G\u001b[0K⠏\u001b[1G\u001b[0K⠋\u001b[1G\u001b[0K⠙\u001b[1G\u001b[0K⠹\u001b[1G\u001b[0K⠸\u001b[1G\u001b[0K⠼\u001b[1G\u001b[0K⠴\u001b[1G\u001b[0K⠦\u001b[1G\u001b[0K⠧\u001b[1G\u001b[0K⠇\u001b[1G\u001b[0Knpm warn deprecated rimraf@2.7.1: Rimraf versions prior to v4 are no longer supported
\u001b[1G\u001b[0K⠇\u001b[1G\u001b[0K⠏\u001b[1G\u001b[0K⠋\u001b[1G\u001b[0Knpm warn deprecated osenv@0.1.5: This package is no longer supported.
\u001b[1G\u001b[0K⠋\u001b[1G\u001b[0K⠙\u001b[1G\u001b[0K⠹\u001b[1G\u001b[0K⠸\u001b[1G\u001b[0K⠼\u001b[1G\u001b[0Knpm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
\u001b[1G\u001b[0K⠼\u001b[1G\u001b[0K⠴\u001b[1G\u001b[0Knpm warn deprecated glob@7.1.7: Glob versions prior to v9 are no longer supported
\u001b[1G\u001b[0K⠴\u001b[1G\u001b[0K⠦\u001b[1G\u001b[0K⠧\u001b[1G\u001b[0K⠇\u001b[1G\u001b[0K⠏\u001b[1G\u001b[0K⠋\u001b[1G\u001b[0K⠙\u001b[1G\u001b[0K⠹\u001b[1G\u001b[0Knpm warn deprecated glob@7.1.6: Glob versions prior to v9 are no longer supported
\u001b[1G\u001b[0K⠸\u001b[1G\u001b[0K⠼\u001b[1G\u001b[0K⠴\u001b[1G\u001b[0K⠦\u001b[1G\u001b[0K⠧\u001b[1G\u001b[0K⠇\u001b[1G\u001b[0K⠏\u001b[1G\u001b[0K⠋\u001b[1G\u001b[0K⠙\u001b[1G\u001b[0K⠹\u001b[1G\u001b[0K⠸\u001b[1G\u001b[0K⠼\u001b[1G\u001b[0K⠴\u001b[1G\u001b[0K⠦\u001b[1G\u001b[0K⠧\u001b[1G\u001b[0K⠇\u001b[1G\u001b[0K⠏\u001b[1G\u001b[0K⠋\u001b[1G\u001b[0K⠙\u001b[1G\u001b[0K⠹\u001b[1G\u001b[0K⠸\u001b[1G\u001b[0K⠼\u001b[1G\u001b[0K⠴\u001b[1G\u001b[0K⠦\u001b[1G\u001b[0K⠧\u001b[1G\u001b[0K⠇\u001b[1G\u001b[0K⠏\u001b[1G\u001b[0K⠋\u001b[1G\u001b[0K⠙\u001b[1G\u001b[0K⠹\u001b[1G\u001b[0K⠸\u001b[1G\u001b[0K⠼\u001b[1G\u001b[0K⠴\u001b[1G\u001b[0K⠦\u001b[1G\u001b[0K⠧\u001b[1G\u001b[0K⠇\u001b[1G\u001b[0K⠏\u001b[1G\u001b[0K⠋\u001b[1G\u001b[0K⠙\u001b[1G\u001b[0K⠹\u001b[1G\u001b[0K⠸\u001b[1G\u001b[0K⠼\u001b[1G\u001b[0K⠴\u001b[1G\u001b[0K⠦\u001b[1G\u001b[0K⠧\u001b[1G\u001b[0K⠇\u001b[1G\u001b[0K⠏\u001b[1G\u001b[0K⠋\u001b[1G\u001b[0K⠙\u001b[1G\u001b[0K⠹\u001b[1G\u001b[0K⠸\u001b[1G\u001b[0K⠼\u001b[1G\u001b[0K⠴\u001b[1G\u001b[0K⠦\u001b[1G\u001b[0K⠧\u001b[1G\u001b[0K⠇\u001b[1G\u001b[0K⠏\u001b[1G\u001b[0K⠋\u001b[1G\u001b[0K⠙\u001b[1G\u001b[0K⠹\u001b[1G\u001b[0K⠸\u001b[1G\u001b[0K⠼\u001b[1G\u001b[0K⠴\u001b[1G\u001b[0K⠦\u001b[1G\u001b[0K⠧\u001b[1G\u001b[0K⠇\u001b[1G\u001b[0K⠏\u001b[1G\u001b[0K⠋\u001b[1G\u001b[0K⠙\u001b[1G\u001b[0K⠹\u001b[1G\u001b[0K⠸\u001b[1G\u001b[0K⠼\u001b[1G\u001b[0K⠴\u001b[1G\u001b[0K⠦\u001b[1G\u001b[0K⠧\u001b[1G\u001b[0K⠇\u001b[1G\u001b[0K⠏\u001b[1G\u001b[0K⠋\u001b[1G\u001b[0K⠙\u001b[1G\u001b[0K⠹\u001b[1G\u001b[0K⠸\u001b[1G\u001b[0K⠼\u001b[1G\u001b[0K⠴\u001b[1G\u001b[0K⠦\u001b[1G\u001b[0K⠧\u001b[1G\u001b[0K⠇\u001b[1G\u001b[0K⠏\u001b[1G\u001b[0K⠋\u001b[1G\u001b[0K⠙\u001b[1G\u001b[0K⠹\u001b[1G\u001b[0K⠸\u001b[1G\u001b[0K⠼\u001b[1G\u001b[0K⠴\u001b[1G\u001b[0K⠦\u001b[1G\u001b[0K⠧\u001b[1G\u001b[0K
> eolang@0.0.0 postinstall
> node scripts/postinstall.js

\u001b[1G\u001b[0K⠧\u001b[1G\u001b[0KDevelopment environment detected, running patch-package...
\u001b[1mpatch-package\u001b[22m 8.0.1
Applying patches...
\u001b[1mgrunt-mocha-cli\u001b[22m@7.0.0 \u001b[32m✔\u001b[39m
\u001b[1G\u001b[0K⠙\u001b[1G\u001b[0K
added 381 packages, and audited 382 packages in 12s
\u001b[1G\u001b[0K⠙\u001b[1G\u001b[0K
\u001b[1G\u001b[0K⠙\u001b[1G\u001b[0K83 packages are looking for funding
\u001b[1G\u001b[0K⠙\u001b[1G\u001b[0K  run `npm fund` for details
\u001b[1G\u001b[0K⠙\u001b[1G\u001b[0K
4 vulnerabilities (1 moderate, 3 high)

To address all issues (including breaking changes), run:
  npm audit fix --force

Run `npm audit` for details.
\u001b[1G\u001b[0K⠙\u001b[1G\u001b[0Knpm notice
npm notice New major version of npm available! 10.8.2 -> 11.6.2
npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.6.2
npm notice To update run: npm install -g npm@11.6.2
npm notice
\u001b[1G\u001b[0K⠙\u001b[1G\u001b[0K\u001b[1G\u001b[0K⠙\u001b[1G\u001b[0K⠹\u001b[1G\u001b[0K⠸\u001b[1G\u001b[0K⠼\u001b[1G\u001b[0K⠴\u001b[1G\u001b[0K⠦\u001b[1G\u001b[0K⠧\u001b[1G\u001b[0Knpm error code ERESOLVE
\u001b[1G\u001b[0K⠧\u001b[1G\u001b[0Knpm error ERESOLVE could not resolve
\u001b[1G\u001b[0K⠧\u001b[1G\u001b[0Knpm error
\u001b[1G\u001b[0K⠧\u001b[1G\u001b[0Knpm error While resolving: @langchain/openai@0.6.16
npm error Found: @langchain/core@1.0.1
npm error node_modules/@langchain/core
npm error   @langchain/core@"^1.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @langchain/core@">=0.3.68 <0.4.0" from @langchain/openai@0.6.16
npm error node_modules/@langchain/openai
npm error   @langchain/openai@"^0.6.0" from the root project
npm error
npm error Conflicting peer dependency: @langchain/core@0.3.78
npm error node_modules/@langchain/core
npm error   peer @langchain/core@">=0.3.68 <0.4.0" from @langchain/openai@0.6.16
npm error   node_modules/@langchain/openai
npm error     @langchain/openai@"^0.6.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
\u001b[1G\u001b[0K⠧\u001b[1G\u001b[0Knpm error
npm error
npm error For a full report see:
npm error /home/r/.npm/_logs/2025-10-18T02_53_50_862Z-eresolve-report.txt
\u001b[1G\u001b[0K⠧\u001b[1G\u001b[0Knpm error A complete log of this run can be found in: /home/r/.npm/_logs/2025-10-18T02_53_50_862Z-debug-0.log
\u001b[1G\u001b[0K⠧\u001b[1G\u001b[0Kcontainer 8ab5fd9526198198bf74efca6bf9473e61964c49adb77b577381bf03f47f9597 is dead
Sat Oct 18 02:54:32 UTC 2025

@renovate renovate bot force-pushed the renovate/langchain-core-1.x branch from 66f87fd to 55cbf61 Compare October 21, 2025 11:45
@renovate renovate bot changed the title fix(deps): update dependency @langchain/core to v1 fix(deps): update dependency @langchain/core to v1 - autoclosed Oct 27, 2025
@renovate renovate bot closed this Oct 27, 2025
@renovate renovate bot deleted the renovate/langchain-core-1.x branch October 27, 2025 18:59
@renovate renovate bot changed the title fix(deps): update dependency @langchain/core to v1 - autoclosed fix(deps): update dependency @langchain/core to v1 Oct 27, 2025
@renovate renovate bot reopened this Oct 27, 2025
@renovate renovate bot force-pushed the renovate/langchain-core-1.x branch 3 times, most recently from 174613c to 200f8fe Compare October 28, 2025 03:27
@renovate renovate bot force-pushed the renovate/langchain-core-1.x branch 2 times, most recently from ce914d0 to 761ffa9 Compare November 10, 2025 16:57
@renovate renovate bot force-pushed the renovate/langchain-core-1.x branch 2 times, most recently from 0fb5bba to a9ea1f5 Compare November 18, 2025 20:08
@renovate renovate bot force-pushed the renovate/langchain-core-1.x branch from a9ea1f5 to 253ef20 Compare November 24, 2025 16:51
@renovate renovate bot force-pushed the renovate/langchain-core-1.x branch from 253ef20 to dcdf8b6 Compare December 2, 2025 04:53
@renovate renovate bot force-pushed the renovate/langchain-core-1.x branch 3 times, most recently from 7ace111 to 83ead7e Compare December 19, 2025 01:50
@renovate renovate bot force-pushed the renovate/langchain-core-1.x branch 4 times, most recently from 64012f1 to 5b016bf Compare January 7, 2026 03:23
@renovate renovate bot force-pushed the renovate/langchain-core-1.x branch from 5b016bf to 0442b48 Compare January 8, 2026 16:43
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.

3 participants