Skip to content

fix(deps): update dependency langchain to v1#2730

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/langchain-1.x
Open

fix(deps): update dependency langchain to v1#2730
renovate[bot] wants to merge 1 commit intomainfrom
renovate/langchain-1.x

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Nov 25, 2025

This PR contains the following updates:

Package Change Age Confidence
langchain (source, changelog) ^0.3.11^1.0.0 age confidence

Configuration

📅 Schedule: Branch creation - "every weekend" in timezone US/Eastern, Automerge - At any time (no schedule defined).

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

Rebasing: Whenever PR is behind base branch, 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 Nov 25, 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: poetry.lock
Updating dependencies
Resolving dependencies...


    Because no versions of langchain match >1.0.0,<1.0.1 || >1.0.1,<1.0.2 || >1.0.2,<1.0.3 || >1.0.3,<1.0.4 || >1.0.4,<1.0.5 || >1.0.5,<1.0.6 || >1.0.6,<1.0.7 || >1.0.7,<1.0.8 || >1.0.8,<1.1.0 || >1.1.0,<1.1.1 || >1.1.1,<1.1.2 || >1.1.2,<1.1.3 || >1.1.3,<1.2.0 || >1.2.0,<1.2.1 || >1.2.1,<1.2.2 || >1.2.2,<1.2.3 || >1.2.3,<1.2.4 || >1.2.4,<1.2.6 || >1.2.6,<1.2.7 || >1.2.7,<1.2.8 || >1.2.8,<1.2.9 || >1.2.9,<1.2.10 || >1.2.10,<2.0.0
 and langchain (1.0.0) depends on langchain-core (>=1.0.0,<2.0.0), langchain (>=1.0.0,<1.0.1 || >1.0.1,<1.0.2 || >1.0.2,<1.0.3 || >1.0.3,<1.0.4 || >1.0.4,<1.0.5 || >1.0.5,<1.0.6 || >1.0.6,<1.0.7 || >1.0.7,<1.0.8 || >1.0.8,<1.1.0 || >1.1.0,<1.1.1 || >1.1.1,<1.1.2 || >1.1.2,<1.1.3 || >1.1.3,<1.2.0 || >1.2.0,<1.2.1 || >1.2.1,<1.2.2 || >1.2.2,<1.2.3 || >1.2.3,<1.2.4 || >1.2.4,<1.2.6 || >1.2.6,<1.2.7 || >1.2.7,<1.2.8 || >1.2.8,<1.2.9 || >1.2.9,<1.2.10 || >1.2.10,<2.0.0) requires langchain-core (>=1.0.0,<2.0.0).
    And because langchain (1.0.1) depends on langchain-core (>=1.0.0,<2.0.0)
 and langchain (1.0.2) depends on langchain-core (>=1.0.0,<2.0.0), langchain (>=1.0.0,<1.0.3 || >1.0.3,<1.0.4 || >1.0.4,<1.0.5 || >1.0.5,<1.0.6 || >1.0.6,<1.0.7 || >1.0.7,<1.0.8 || >1.0.8,<1.1.0 || >1.1.0,<1.1.1 || >1.1.1,<1.1.2 || >1.1.2,<1.1.3 || >1.1.3,<1.2.0 || >1.2.0,<1.2.1 || >1.2.1,<1.2.2 || >1.2.2,<1.2.3 || >1.2.3,<1.2.4 || >1.2.4,<1.2.6 || >1.2.6,<1.2.7 || >1.2.7,<1.2.8 || >1.2.8,<1.2.9 || >1.2.9,<1.2.10 || >1.2.10,<2.0.0) requires langchain-core (>=1.0.0,<2.0.0).
    And because langchain (1.0.3) depends on langchain-core (>=1.0.0,<2.0.0)
 and langchain (1.0.4) depends on langchain-core (>=1.0.0,<2.0.0), langchain (>=1.0.0,<1.0.5 || >1.0.5,<1.0.6 || >1.0.6,<1.0.7 || >1.0.7,<1.0.8 || >1.0.8,<1.1.0 || >1.1.0,<1.1.1 || >1.1.1,<1.1.2 || >1.1.2,<1.1.3 || >1.1.3,<1.2.0 || >1.2.0,<1.2.1 || >1.2.1,<1.2.2 || >1.2.2,<1.2.3 || >1.2.3,<1.2.4 || >1.2.4,<1.2.6 || >1.2.6,<1.2.7 || >1.2.7,<1.2.8 || >1.2.8,<1.2.9 || >1.2.9,<1.2.10 || >1.2.10,<2.0.0) requires langchain-core (>=1.0.0,<2.0.0).
    And because langchain (1.0.5) depends on langchain-core (>=1.0.4,<2.0.0)
 and langchain (1.0.6) depends on langchain-core (>=1.0.4,<2.0.0), langchain (>=1.0.0,<1.0.7 || >1.0.7,<1.0.8 || >1.0.8,<1.1.0 || >1.1.0,<1.1.1 || >1.1.1,<1.1.2 || >1.1.2,<1.1.3 || >1.1.3,<1.2.0 || >1.2.0,<1.2.1 || >1.2.1,<1.2.2 || >1.2.2,<1.2.3 || >1.2.3,<1.2.4 || >1.2.4,<1.2.6 || >1.2.6,<1.2.7 || >1.2.7,<1.2.8 || >1.2.8,<1.2.9 || >1.2.9,<1.2.10 || >1.2.10,<2.0.0) requires langchain-core (>=1.0.0,<2.0.0).
    And because langchain (1.0.7) depends on langchain-core (>=1.0.4,<2.0.0)
 and langchain (1.0.8) depends on langchain-core (>=1.0.6,<2.0.0), langchain (>=1.0.0,<1.1.0 || >1.1.0,<1.1.1 || >1.1.1,<1.1.2 || >1.1.2,<1.1.3 || >1.1.3,<1.2.0 || >1.2.0,<1.2.1 || >1.2.1,<1.2.2 || >1.2.2,<1.2.3 || >1.2.3,<1.2.4 || >1.2.4,<1.2.6 || >1.2.6,<1.2.7 || >1.2.7,<1.2.8 || >1.2.8,<1.2.9 || >1.2.9,<1.2.10 || >1.2.10,<2.0.0) requires langchain-core (>=1.0.0,<2.0.0).
    And because langchain (1.1.0) depends on langchain-core (>=1.1.0,<2.0.0)
 and langchain (1.1.1) depends on langchain-core (>=1.1.0,<2.0.0), langchain (>=1.0.0,<1.1.2 || >1.1.2,<1.1.3 || >1.1.3,<1.2.0 || >1.2.0,<1.2.1 || >1.2.1,<1.2.2 || >1.2.2,<1.2.3 || >1.2.3,<1.2.4 || >1.2.4,<1.2.6 || >1.2.6,<1.2.7 || >1.2.7,<1.2.8 || >1.2.8,<1.2.9 || >1.2.9,<1.2.10 || >1.2.10,<2.0.0) requires langchain-core (>=1.0.0,<2.0.0).
    And because langchain (1.1.2) depends on langchain-core (>=1.1.0,<2.0.0)
 and langchain (1.1.3) depends on langchain-core (>=1.1.2,<2.0.0), langchain (>=1.0.0,<1.2.0 || >1.2.0,<1.2.1 || >1.2.1,<1.2.2 || >1.2.2,<1.2.3 || >1.2.3,<1.2.4 || >1.2.4,<1.2.6 || >1.2.6,<1.2.7 || >1.2.7,<1.2.8 || >1.2.8,<1.2.9 || >1.2.9,<1.2.10 || >1.2.10,<2.0.0) requires langchain-core (>=1.0.0,<2.0.0).
    And because langchain (1.2.0) depends on langchain-core (>=1.2.1,<2.0.0)
 and langchain (1.2.1) depends on langchain-core (>=1.2.1,<2.0.0), langchain (>=1.0.0,<1.2.2 || >1.2.2,<1.2.3 || >1.2.3,<1.2.4 || >1.2.4,<1.2.6 || >1.2.6,<1.2.7 || >1.2.7,<1.2.8 || >1.2.8,<1.2.9 || >1.2.9,<1.2.10 || >1.2.10,<2.0.0) requires langchain-core (>=1.0.0,<2.0.0).
    And because langchain (1.2.2) depends on langchain-core (>=1.2.1,<2.0.0)
 and langchain (1.2.3) depends on langchain-core (>=1.2.1,<2.0.0), langchain (>=1.0.0,<1.2.4 || >1.2.4,<1.2.6 || >1.2.6,<1.2.7 || >1.2.7,<1.2.8 || >1.2.8,<1.2.9 || >1.2.9,<1.2.10 || >1.2.10,<2.0.0) requires langchain-core (>=1.0.0,<2.0.0).
    And because langchain (1.2.4) depends on langchain-core (>=1.2.1,<2.0.0)
 and langchain (1.2.6) depends on langchain-core (>=1.2.7,<2.0.0), langchain (>=1.0.0,<1.2.7 || >1.2.7,<1.2.8 || >1.2.8,<1.2.9 || >1.2.9,<1.2.10 || >1.2.10,<2.0.0) requires langchain-core (>=1.0.0,<2.0.0).
    And because langchain (1.2.7) depends on langchain-core (>=1.2.7,<2.0.0)
 and langchain (1.2.8) depends on langchain-core (>=1.2.8,<2.0.0), langchain (>=1.0.0,<1.2.9 || >1.2.9,<1.2.10 || >1.2.10,<2.0.0) requires langchain-core (>=1.0.0,<2.0.0).
(1) So, because langchain (1.2.9) depends on langchain-core (>=1.2.9,<2.0.0)
 and langchain (1.2.10) depends on langchain-core (>=1.2.10,<2.0.0), langchain (>=1.0.0,<2.0.0) requires langchain-core (>=1.0.0,<2.0.0).

    Because no versions of langchain-experimental match >0.3.4,<0.3.5rc1 || >0.3.5rc1,<0.4.0
 and langchain-experimental (0.3.5rc1) depends on langchain-core (>=0.3.28,<1.0.0), langchain-experimental (>0.3.4,<0.4.0) requires langchain-core (>=0.3.28,<1.0.0).
    And because langchain-experimental (0.3.4) depends on langchain-core (>=0.3.28,<0.4.0), langchain-experimental (>=0.3.4,<0.4.0) requires langchain-core (>=0.3.28,<1.0.0).
    And because langchain (>=1.0.0,<2.0.0) requires langchain-core (>=1.0.0,<2.0.0) (1), langchain (>=1.0.0,<2.0.0) is incompatible with langchain-experimental (>=0.3.4,<0.4.0)
    So, because mit-learn depends on both langchain (^1.0.0) and langchain-experimental (^0.3.4), version solving failed.

@renovate renovate bot force-pushed the renovate/langchain-1.x branch 4 times, most recently from f2ad1d3 to 5186db1 Compare December 1, 2025 16:18
@renovate renovate bot force-pushed the renovate/langchain-1.x branch 13 times, most recently from f00e2c3 to e0508f7 Compare December 12, 2025 21:23
@renovate renovate bot force-pushed the renovate/langchain-1.x branch 12 times, most recently from deb5787 to 1fc8817 Compare December 18, 2025 04:00
@renovate renovate bot force-pushed the renovate/langchain-1.x branch 4 times, most recently from 9d7d761 to 91f52b0 Compare February 5, 2026 19:26
@renovate renovate bot force-pushed the renovate/langchain-1.x branch 2 times, most recently from 5aef3b5 to f4c0aa1 Compare February 5, 2026 20:18
@renovate renovate bot force-pushed the renovate/langchain-1.x branch 3 times, most recently from b58b525 to f2f0206 Compare February 6, 2026 17:37
@renovate renovate bot force-pushed the renovate/langchain-1.x branch from f2f0206 to 9bfe9c4 Compare February 6, 2026 18:44
@@ -57,7 +57,7 @@ html5lib = "^1.1"
ipython = "^9.0.0"
isodate = "^0.7.2"
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: Upgrading langchain to ^1.0.0 conflicts with langchain-experimental ^0.3.4, which requires an older langchain-community version. This will cause dependency resolution to fail.
Severity: CRITICAL

Suggested Fix

To resolve the dependency conflict, update langchain-experimental in pyproject.toml to a version compatible with langchain ^1.0.0, likely ^0.4.x or higher. After updating, run poetry lock and poetry install to verify the dependencies can be resolved successfully.

Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: pyproject.toml#L58

Potential issue: The update to `langchain="^1.0.0"` in `pyproject.toml` introduces a
dependency conflict. The project also depends on `langchain-experimental="^0.3.4"`,
which has a strict requirement for `langchain-community` to be a version less than
`0.4.0`. However, `langchain 1.0.0` requires a newer, incompatible version of
`langchain-community`. This conflict will prevent the project's dependencies from being
installed, causing the build or deployment process to fail immediately.

@renovate renovate bot force-pushed the renovate/langchain-1.x branch 14 times, most recently from 334ffed to 504bd12 Compare February 11, 2026 19:49
@renovate renovate bot force-pushed the renovate/langchain-1.x branch from 504bd12 to fd06f83 Compare February 15, 2026 11: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.

0 participants