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

[PR #2436] [MERGED] feat: docs for api migration #2425

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

📋 Pull Request Information

Original PR: https://github.com/langchain-ai/docs/pull/2436
Author: @ericdong-langchain
Created: 2/2/2026
Status: ✅ Merged
Merged: 2/12/2026
Merged by: @ericdong-langchain

Base: main ← Head: ericd/api-deprecation-docs

📝 Commits (6)

  • 5751985 feat: API versioning and migration docs (runs endpoint v1 to v2)
  • f817869 fix: comments
  • 3c0b7bf fix: address comments
  • 024d106 added sdk migration
  • 418be38 Merge branch 'main' into ericd/api-deprecation-docs
  • b2391e2 Merge branch 'main' into ericd/api-deprecation-docs

📊 Changes

4 files changed (+816 additions, -0 deletions)

View changed files

📝 src/docs.json (+8 -0)
➕ src/langsmith/api-v1-v2-overview.mdx (+468 -0)
➕ src/langsmith/endpoint-deprecation.mdx (+136 -0)
➕ src/langsmith/endpoint-migration.mdx (+204 -0)

📄 Description

Overview

3 Pages of docs for migration instructions for v1 to v2 endpoints.

Type of change

Type: [Replace with: New documentation page / Update existing documentation / Fix typo/bug/link/formatting / Remove outdated content / Other]
New Documentation page

Related issues/PRs

  • GitHub issue:
  • Feature PR:
  • Linear issue:
  • Slack thread:

Checklist

  • I have read the contributing guidelines
  • 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

(Internal team members only / optional): Create a preview deployment as necessary using the Create Preview Branch workflow

Additional notes

🔄 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/2436 **Author:** [@ericdong-langchain](https://github.com/ericdong-langchain) **Created:** 2/2/2026 **Status:** ✅ Merged **Merged:** 2/12/2026 **Merged by:** [@ericdong-langchain](https://github.com/ericdong-langchain) **Base:** `main` ← **Head:** `ericd/api-deprecation-docs` --- ### 📝 Commits (6) - [`5751985`](https://github.com/langchain-ai/docs/commit/5751985f782d03ead29fd9f0ca120441b0577b08) feat: API versioning and migration docs (runs endpoint v1 to v2) - [`f817869`](https://github.com/langchain-ai/docs/commit/f817869870b16c93150cfe8c2769005d868cae99) fix: comments - [`3c0b7bf`](https://github.com/langchain-ai/docs/commit/3c0b7bf373c8e9d2b5a8b4344ddfd2e9d5f139f6) fix: address comments - [`024d106`](https://github.com/langchain-ai/docs/commit/024d106bf6829398d99636e7932b04a549c0855a) added sdk migration - [`418be38`](https://github.com/langchain-ai/docs/commit/418be38723b1311a6501a068a6aef609de19a16f) Merge branch 'main' into ericd/api-deprecation-docs - [`b2391e2`](https://github.com/langchain-ai/docs/commit/b2391e24ddcfaf03fd0a1aae1972209bae7559c2) Merge branch 'main' into ericd/api-deprecation-docs ### 📊 Changes **4 files changed** (+816 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `src/docs.json` (+8 -0) ➕ `src/langsmith/api-v1-v2-overview.mdx` (+468 -0) ➕ `src/langsmith/endpoint-deprecation.mdx` (+136 -0) ➕ `src/langsmith/endpoint-migration.mdx` (+204 -0) </details> ### 📄 Description ## Overview <!-- Brief description of what documentation is being added/updated --> 3 Pages of docs for migration instructions for v1 to v2 endpoints. ## Type of change **Type:** [Replace with: New documentation page / Update existing documentation / Fix typo/bug/link/formatting / Remove outdated content / Other] New Documentation page ## Related issues/PRs <!-- Link to related issues, feature PRs, or discussions (if applicable) To automatically close an issue when this PR is merged, use closing keywords: - "closes #123" or "fixes #123" or "resolves #123" For regular references without auto-closing, just use: - "#123" or "See issue #123" Examples: - closes #456 (will auto-close issue #456 when PR is merged) - See #789 for context (will reference but not auto-close issue #789) --> - GitHub issue: - Feature PR: <!-- For LangChain employees, if applicable: --> - Linear issue: - Slack thread: ## Checklist <!-- Put an 'x' in all boxes that apply --> - [x] I have read the [contributing guidelines](README.md) - [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 (Internal team members only / optional): Create a preview deployment as necessary using the [Create Preview Branch workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml) ## Additional notes <!-- Any other information that would be helpful for reviewers --> --- <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-02-17 17:23:24 -05:00
yindo closed this issue 2026-02-17 17:23:24 -05:00
yindo changed title from [PR #2436] feat: docs for api migration to [PR #2436] [MERGED] feat: docs for api migration 2026-06-05 18:18:33 -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#2425
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?