langchain-ai/langgraph
1
0
Fork 0
mirror of https://github.com/langchain-ai/langgraph.git synced 2026-07-15 12:35:43 -04:00
Code Issues 314 Packages Projects Releases 17 Wiki Activity

Incompatibility between langgraph-cli and langgraph-api >= 0.7.0 #1123

New Issue
Closed
opened 2026-02-20 17:43:10 -05:00 by yindo · 0 comments
yindo commented 2026-02-20 17:43:10 -05:00
Owner
Copy Link
Copy Source

Originally created by @farouk09 on GitHub (Jan 21, 2026).

Description

There is a dependency conflict between langgraph-cli and langgraph-api when using langgraph-api version 0.7.0 or higher. The langgraph-cli package currently supports langgraph-api versions up to <0.7.0, which causes issues when trying to use the latest langgraph-api.

Steps to Reproduce

  1. Add langgraph-api>=0.7.3 as a dependency.
  2. Attempt to resolve dependencies with langgraph-cli.

Observed Behavior

Dependency resolution fails with the following error:

No solution found when resolving dependencies:
  Because only langgraph-cli[inmem]<=0.4.11 is available and langgraph-cli[inmem]==0.4.11 depends on langgraph-api>=0.5.35,<0.7.0, we can conclude that langgraph-cli[inmem]>=0.4.11 depends on langgraph-api>=0.5.35,<0.7.0.
  And because mycurator-backend:dev depends on langgraph-cli[inmem]>=0.4.11 and your project depends on langgraph-api>=0.7.3, we can conclude that mycurator-backend[dev] and mycurator-backend:dev are incompatible.

Expected Behavior

langgraph-cli should support langgraph-api version 0.7.0 and higher.

Suggested Solution

Please update langgraph-cli to support langgraph-api >= 0.7.0.

Additional Context

This issue blocks projects that require the latest langgraph-api features. Let me know if further details are needed.

Originally created by @farouk09 on GitHub (Jan 21, 2026). ### Description There is a dependency conflict between `langgraph-cli` and `langgraph-api` when using `langgraph-api` version 0.7.0 or higher. The `langgraph-cli` package currently supports `langgraph-api` versions up to <0.7.0, which causes issues when trying to use the latest `langgraph-api`. ### Steps to Reproduce 1. Add `langgraph-api>=0.7.3` as a dependency. 2. Attempt to resolve dependencies with `langgraph-cli`. ### Observed Behavior Dependency resolution fails with the following error: ``` No solution found when resolving dependencies: Because only langgraph-cli[inmem]<=0.4.11 is available and langgraph-cli[inmem]==0.4.11 depends on langgraph-api>=0.5.35,<0.7.0, we can conclude that langgraph-cli[inmem]>=0.4.11 depends on langgraph-api>=0.5.35,<0.7.0. And because mycurator-backend:dev depends on langgraph-cli[inmem]>=0.4.11 and your project depends on langgraph-api>=0.7.3, we can conclude that mycurator-backend[dev] and mycurator-backend:dev are incompatible. ``` ### Expected Behavior `langgraph-cli` should support `langgraph-api` version 0.7.0 and higher. ### Suggested Solution Please update `langgraph-cli` to support `langgraph-api` >= 0.7.0. ### Additional Context This issue blocks projects that require the latest `langgraph-api` features. Let me know if further details are needed.
yindo closed this issue 2026-02-20 17:43:10 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
agents
awaiting author revision
bug
change
chat models
checkpointer
ci
code quality
code quality
dependencies
documentation
drawing
duplicate
enhancement
good first issue
help wanted
invalid
maintainer
meta
missing information
not maintained by langchain
open-swe-auto
open-swe-max
open-swe-max-auto
pending
performance
pull-request
Mirrored from GitHub Pull Request
 question
requires design
sdk
server
stale
studio
tests
type checking
usage question
v0.5
v1.1
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langchain-ai/langgraph#1123
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?