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

[PR #1399] [MERGED] Clarify Egress Docs #1538

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

📋 Pull Request Information

Original PR: https://github.com/langchain-ai/docs/pull/1399
Author: @romain-priour-lc
Created: 11/13/2025
Status: ✅ Merged
Merged: 11/13/2025
Merged by: @romain-priour-lc

Base: main ← Head: romain/clarify-egress-docs

📝 Commits (3)

📊 Changes

1 file changed (+3 additions, -3 deletions)

View changed files

📝 src/langsmith/self-host-egress.mdx (+3 -3)

📄 Description

Overview

It is unclear that traces are not customer traces, but operational metadata

Type of change

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

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
  • I have gotten approval from the relevant reviewers
  • (Internal team members only / optional) I have created a preview deployment 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/1399 **Author:** [@romain-priour-lc](https://github.com/romain-priour-lc) **Created:** 11/13/2025 **Status:** ✅ Merged **Merged:** 11/13/2025 **Merged by:** [@romain-priour-lc](https://github.com/romain-priour-lc) **Base:** `main` ← **Head:** `romain/clarify-egress-docs` --- ### 📝 Commits (3) - [`e1a6f61`](https://github.com/langchain-ai/docs/commit/e1a6f61bfb29698b7558f1355ff6f7ad28ef667e) clarify egress docs - [`6f6c280`](https://github.com/langchain-ai/docs/commit/6f6c280159bed38aeb2c03945cd4594419317794) rename header - [`73cb85c`](https://github.com/langchain-ai/docs/commit/73cb85c8f0628888264c52a8e4175c493744d92f) spelling fixes ### 📊 Changes **1 file changed** (+3 additions, -3 deletions) <details> <summary>View changed files</summary> 📝 `src/langsmith/self-host-egress.mdx` (+3 -3) </details> ### 📄 Description ## Overview It is unclear that traces are not customer traces, but operational metadata ## Type of change **Type:** [Replace with: New documentation page / Update existing documentation / Fix typo/bug/link/formatting / Remove outdated content / Other] ## 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 --> - [ ] I have read the [contributing guidelines](README.md) - [ ] 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 - I have gotten approval from the relevant reviewers - (Internal team members only / optional) I have created a preview deployment 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:22:28 -05:00
yindo closed this issue 2026-02-17 17:22:28 -05:00
yindo changed title from [PR #1399] Clarify Egress Docs to [PR #1399] [MERGED] Clarify Egress Docs 2026-06-05 18:13:11 -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#1538
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?