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

[PR #2200] [MERGED] chore: publish granular usage change in release notes #2217

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

📋 Pull Request Information

Original PR: https://github.com/langchain-ai/docs/pull/2200
Author: @bvs-langchain
Created: 1/12/2026
Status: ✅ Merged
Merged: 1/12/2026
Merged by: @bvs-langchain

Base: main ← Head: brian/ent-411-granular-usage-release-notes

📝 Commits (1)

  • db5348a chore: publish granular usage change in release notes

📊 Changes

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

View changed files

📝 src/langsmith/self-hosted-changelog.mdx (+1 -0)

📄 Description

Overview

added information about new Granular Usage tab to self-hosted release notes

Type of change

Type: Update existing documentation

Related issues/PRs

  • GitHub issue:
  • Feature PR:
  • Linear issue: ent-411
  • 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/2200 **Author:** [@bvs-langchain](https://github.com/bvs-langchain) **Created:** 1/12/2026 **Status:** ✅ Merged **Merged:** 1/12/2026 **Merged by:** [@bvs-langchain](https://github.com/bvs-langchain) **Base:** `main` ← **Head:** `brian/ent-411-granular-usage-release-notes` --- ### 📝 Commits (1) - [`db5348a`](https://github.com/langchain-ai/docs/commit/db5348a482a46b5a8db868c5f9a56589d3e7827f) chore: publish granular usage change in release notes ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `src/langsmith/self-hosted-changelog.mdx` (+1 -0) </details> ### 📄 Description ## Overview <!-- Brief description of what documentation is being added/updated --> added information about new Granular Usage tab to self-hosted release notes ## Type of change **Type:** Update existing documentation ## 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: ent-411 - 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:11 -05:00
yindo closed this issue 2026-02-17 17:23:11 -05:00
yindo changed title from [PR #2200] chore: publish granular usage change in release notes to [PR #2200] [MERGED] chore: publish granular usage change in release notes 2026-06-05 18:17:19 -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#2217
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?