langchain-ai/docs
1
0
Fork 0
mirror of https://github.com/langchain-ai/docs.git synced 2026-07-20 08:58:10 -04:00
Code Issues 490 Packages Projects Releases Wiki Activity

[PR #3546] docs(langgraph): add graph version pinning for breaking changes #3590

New Issue
Open
opened 2026-06-05 18:23:35 -04:00 by yindo · 0 comments
yindo commented 2026-06-05 18:23:35 -04:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/langchain-ai/docs/pull/3546
Author: @victorm-lc
Created: 4/10/2026
Status: 🔄 Open

Base: main ← Head: vic/graph-breaking-changes

📝 Commits (1)

  • 4701b32 docs(langgraph): add graph version pinning for breaking changes

📊 Changes

1 file changed (+44 additions, -0 deletions)

View changed files

📝 src/oss/langgraph/graph-api.mdx (+44 -0)

📄 Description

Overview

Updating our graph migration docs to provide some recommendations for handling breaking changes in graph's logic. This includes pinning a graph's version in the graph's internal state, or migrating state from older threads to updated state logic.

Type of change

Type: Update existing documentation

Related issues/PRs

Checklist

  • I have read the contributing guidelines, including the language policy
  • I have tested my changes locally using docs dev
  • All code examples have been tested and work correctly
  • I have used root relative paths for internal links
  • I have updated navigation in src/docs.json if needed

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/langchain-ai/docs/pull/3546 **Author:** [@victorm-lc](https://github.com/victorm-lc) **Created:** 4/10/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `vic/graph-breaking-changes` --- ### 📝 Commits (1) - [`4701b32`](https://github.com/langchain-ai/docs/commit/4701b32f805d150810a7e4d32abb26e95859416f) docs(langgraph): add graph version pinning for breaking changes ### 📊 Changes **1 file changed** (+44 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `src/oss/langgraph/graph-api.mdx` (+44 -0) </details> ### 📄 Description ## Overview <!-- Brief description of what documentation is being added/updated --> Updating our graph migration docs to provide some recommendations for handling breaking changes in graph's logic. This includes pinning a graph's version in the graph's internal state, or migrating state from older threads to updated state logic. ## Type of change **Type:** Update existing documentation ## Related issues/PRs <!-- For LangChain employees, if applicable: --> - Slack thread: https://langchain.slack.com/archives/C09ET5XJDMY/p1774976626622869 ## Checklist <!-- Put an 'x' in all boxes that apply --> - [x] I have read the [contributing guidelines](README.md), including the [language policy](https://docs.langchain.com/oss/python/contributing/overview#language-policy) - [x] I have tested my changes locally using `docs dev` - [x] All code examples have been tested and work correctly - [x] I have used **root relative** paths for internal links - [x] I have updated navigation in `src/docs.json` if needed --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-06-05 18:23:35 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
deepagents
docs-infra
external
external
help wanted
integration
internal
internal
javascript
js/ts
langchain
langgraph
langsmith
needs-title
pull-request
Mirrored from GitHub Pull Request
 python
reference
No Label pull-request
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/docs#3590
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?