langchain-ai/langgraphjs
1
0
Fork 0
mirror of https://github.com/langchain-ai/langgraphjs.git synced 2026-07-23 01:26:57 -04:00
Code Issues 108 Packages Projects Releases 20 Wiki Activity

api_version field in langgraph.json is not respected by @langchain/langgraph-cli #404

New Issue
Open
opened 2026-02-15 18:16:28 -05:00 by yindo · 0 comments
yindo commented 2026-02-15 18:16:28 -05:00
Owner
Copy Link
Copy Source

Originally created by @jessieibarra on GitHub (Feb 10, 2026).

Checked other resources

  • I added a very descriptive title to this issue.
  • I searched the LangGraph.js documentation with the integrated search.
  • I used the GitHub search to find a similar question and didn't find it.
  • I am sure that this is a bug in LangGraph.js rather than my code.
  • The bug is not resolved by updating to the latest stable version of LangGraph (or the specific integration package).

Example Code

  1. Create a TypeScript LangGraph project with this langgraph.json:
{
  "api_version": "0.6.39",
  "graphs": {
    "supervisor_graph": "./src/graphs/supervisorGraph.ts:app"
  },
  "node_version": "22",
  "env": "./.env",
  "dependencies": ["."]
}
  1. Build with the JS CLI:
npx @langchain/langgraph-cli build -c langgraph.json
  1. Inspect the built image or run it and check logs.

Expected: Base image langchain/langgraphjs-api:0.6.39-node22, logs show langgraph_api_version=0.6.39
Actual: Base image langchain/langgraphjs-api:22 (resolving to latest), logs show langgraph_api_version=0.7.28

Error Message and Stack Trace (if applicable)

No response

Description

Note: Claude Opus wrote this

Users cannot pin a specific API server version when building TypeScript graphs with the JS CLI. This is a parity gap with the Python CLI, which correctly respects api_version for both Python and TypeScript projects.

Root Cause

Two locations in @langchain/langgraph-cli need changes:

  1. src/utils/config.mts — BaseConfigSchema Zod schema does not include api_version:
// Current: no api_version field
const BaseConfigSchema = z.object({
  // ...
  _INTERNAL_docker_tag: z.string().optional(),
  // ...
});
  1. src/docker/docker.mts — getBaseImage() does not use api_version when constructing the image tag:
// Current: falls back to node_version, ignoring api_version
export function getBaseImage(config: Config) {
  if ("node_version" in config) {
    return `langchain/langgraphjs-api:${
      config._INTERNAL_docker_tag || config.node_version
    }`;
  }
  // ...
}

Suggested Fix

  1. Add api_version to the Zod schema:
api_version: z.string().optional(),
  1. Update getBaseImage() to use it:
export function getBaseImage(config: Config) {
  if ("node_version" in config) {
    const tag = config._INTERNAL_docker_tag
      || (config.api_version ? `${config.api_version}-node${config.node_version}` : config.node_version);
    return `langchain/langgraphjs-api:${tag}`;
  }
  // ...
}

System Info

Node version: v25.2.1
Operating system: darwin arm64
Package manager: npm
Package manager version: N/A

@langchain/core -> @1.1.16, , @"^1.1.16", @"^1.0.1", @"^1.1.15"
langsmith -> @0.4.8, , @"^0.4.8", @">=0.4.0
zod -> @4.3.6, , @"^3.25.76, @"^3.25.32
@langchain/langgraph -> @1.1.1, , @"^1.1.1"
@langchain/langgraph-checkpoint -> @1.0.0, , @"^1.0.0"
@langchain/langgraph-sdk -> @1.5.5, , @"~1.5.5"

Originally created by @jessieibarra on GitHub (Feb 10, 2026). ### Checked other resources - [x] I added a very descriptive title to this issue. - [x] I searched the LangGraph.js documentation with the integrated search. - [x] I used the GitHub search to find a similar question and didn't find it. - [x] I am sure that this is a bug in LangGraph.js rather than my code. - [x] The bug is not resolved by updating to the latest stable version of LangGraph (or the specific integration package). ### Example Code 1. Create a TypeScript LangGraph project with this `langgraph.json`: ```json { "api_version": "0.6.39", "graphs": { "supervisor_graph": "./src/graphs/supervisorGraph.ts:app" }, "node_version": "22", "env": "./.env", "dependencies": ["."] } ``` 2. Build with the JS CLI: ```bash npx @langchain/langgraph-cli build -c langgraph.json ``` 3. Inspect the built image or run it and check logs. **Expected:** Base image `langchain/langgraphjs-api:0.6.39-node22`, logs show `langgraph_api_version=0.6.39` **Actual:** Base image `langchain/langgraphjs-api:22` (resolving to latest), logs show `langgraph_api_version=0.7.28` ### Error Message and Stack Trace (if applicable) _No response_ ### Description Note: Claude Opus wrote this Users cannot pin a specific API server version when building TypeScript graphs with the JS CLI. This is a parity gap with the Python CLI, which correctly respects `api_version` for both Python and TypeScript projects. ### Root Cause Two locations in `@langchain/langgraph-cli` need changes: 1. **`src/utils/config.mts`** — `BaseConfigSchema` Zod schema does not include `api_version`: ```typescript // Current: no api_version field const BaseConfigSchema = z.object({ // ... _INTERNAL_docker_tag: z.string().optional(), // ... }); ``` 2. **`src/docker/docker.mts`** — `getBaseImage()` does not use `api_version` when constructing the image tag: ```typescript // Current: falls back to node_version, ignoring api_version export function getBaseImage(config: Config) { if ("node_version" in config) { return `langchain/langgraphjs-api:${ config._INTERNAL_docker_tag || config.node_version }`; } // ... } ``` ### Suggested Fix 1. Add `api_version` to the Zod schema: ```typescript api_version: z.string().optional(), ``` 2. Update `getBaseImage()` to use it: ```typescript export function getBaseImage(config: Config) { if ("node_version" in config) { const tag = config._INTERNAL_docker_tag || (config.api_version ? `${config.api_version}-node${config.node_version}` : config.node_version); return `langchain/langgraphjs-api:${tag}`; } // ... } ``` ### System Info Node version: v25.2.1 Operating system: darwin arm64 Package manager: npm Package manager version: N/A -------------------- @langchain/core -> @1.1.16, , @"^1.1.16", @"^1.0.1", @"^1.1.15" langsmith -> @0.4.8, , @"^0.4.8", @">=0.4.0 zod -> @4.3.6, , @"^3.25.76, @"^3.25.32 @langchain/langgraph -> @1.1.1, , @"^1.1.1" @langchain/langgraph-checkpoint -> @1.0.0, , @"^1.0.0" @langchain/langgraph-sdk -> @1.5.5, , @"~1.5.5"
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
checkpointer
docs-needed
documentation
enhancement
good first issue
good writeup
help wanted
invalid
langgraph-supervisor
open-swe-auto
platform
prebuilt
pull-request
Mirrored from GitHub Pull Request
 question
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/langgraphjs#404
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?