Clarification on Official Container Images, Supported Python Versions, and the Recommended LangGraph Deployment Path

OSS Product Help LangChain
, ,
1

Hi team,

We’re trying to align our containerization strategy with the officially supported approach for LangChain/LangGraph, and we need clarification on what the upstream-supported path looks like today.

Context

  • The last published langchain/langchain Docker Hub image appears to be from ~2023 and no longer updated.

  • LangGraph seems to be the current recommended mechanism for deployable, containerized applications.

  • The only actively updated images we can find are:

    • langchain/langgraph-api:3.11

    • langchain/langgraph-api:3.12

    • langchain/langgraphjs-api:20

Before we move forward, we want to make sure we’re following the intended upstream direction rather than recreating an out-of-date image or relying on deprecated tooling.

Questions

  1. Are the legacy langchain/langchain Docker images officially deprecated or unsupported?
    We want to confirm whether they should be considered EOL.

  2. Are the LangGraph API base images the only officially supported container images going forward?
    i.e., is all containerized deployment expected to happen through LangGraph?

  3. Which Python versions are officially supported for LangGraph-based container deployments?
    Currently we see 3.11 and `3.12 — is this the complete support matrix?

  4. Is the LangGraph CLI (and its build pipeline) now the authoritative way to build production images?
    Or is there another recommended pattern we should follow?

We want to ensure we build on top of the supported path and avoid reconstructing deprecated images.

Thanks for your help, any guidance or official stance would be appreciated.