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 #4127] [MERGED] Backfill release-image markers into the self-hosted changelog #4125

New Issue
Closed
opened 2026-06-05 19:12:50 -04:00 by yindo · 0 comments
yindo commented 2026-06-05 19:12:50 -04:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/langchain-ai/docs/pull/4127
Author: @lnhsingh
Created: 5/21/2026
Status: ✅ Merged
Merged: 5/21/2026
Merged by: @lnhsingh

Base: main ← Head: worktree-sh-cl-fix

📝 Commits (2)

  • 88e21f7 add back changelog entries
  • 0e886fc Backfill release-image markers into the self-hosted changelog

📊 Changes

1 file changed (+677 additions, -88 deletions)

View changed files

📝 src/langsmith/self-hosted-changelog.mdx (+677 -88)

📄 Description

Summary

Backfills a {/* langsmith-release-image: <version> <key> */} MDX comment into every <Update> entry of the self-hosted changelog (88 entries). Each marker records the underlying LangSmith image a helm release packages — the image ref from its langchainplus release, or the appVersion string when no ref is published.

Why

The helm-changelog-bot reads these markers (git.parse_logged_release_keys) to deduplicate future releases against entries already in the changelog: a new helm release that repackages an image an existing entry already shipped gets a cross-linked "refer to" note instead of duplicated or placeholder release notes.

The recovery/dedup changelog content already merged to main only carries markers for entries written after the bot change. This backfill extends that coverage to the pre-existing entries, so the bot dedupes against the full history.

The markers are MDX comments — invisible in the rendered page. Verified with make lint_prose (0 errors) and make broken-links (this file not flagged).

AI disclosure

Prepared with assistance from Claude Code; see the Co-Authored-By trailer on the commit.

🔄 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/4127 **Author:** [@lnhsingh](https://github.com/lnhsingh) **Created:** 5/21/2026 **Status:** ✅ Merged **Merged:** 5/21/2026 **Merged by:** [@lnhsingh](https://github.com/lnhsingh) **Base:** `main` ← **Head:** `worktree-sh-cl-fix` --- ### 📝 Commits (2) - [`88e21f7`](https://github.com/langchain-ai/docs/commit/88e21f7611c7b96c4ab4d9fb68c07667babc3e03) add back changelog entries - [`0e886fc`](https://github.com/langchain-ai/docs/commit/0e886fca197de1e466544efe5a7391b9e731be94) Backfill release-image markers into the self-hosted changelog ### 📊 Changes **1 file changed** (+677 additions, -88 deletions) <details> <summary>View changed files</summary> 📝 `src/langsmith/self-hosted-changelog.mdx` (+677 -88) </details> ### 📄 Description ## Summary Backfills a `{/* langsmith-release-image: <version> <key> */}` MDX comment into every `<Update>` entry of the self-hosted changelog (88 entries). Each marker records the underlying LangSmith image a helm release packages — the image ref from its langchainplus release, or the appVersion string when no ref is published. ## Why The `helm-changelog-bot` reads these markers (`git.parse_logged_release_keys`) to deduplicate future releases against entries **already in the changelog**: a new helm release that repackages an image an existing entry already shipped gets a cross-linked "refer to" note instead of duplicated or placeholder release notes. The recovery/dedup changelog content already merged to `main` only carries markers for entries written *after* the bot change. This backfill extends that coverage to the pre-existing entries, so the bot dedupes against the full history. The markers are MDX comments — invisible in the rendered page. Verified with `make lint_prose` (0 errors) and `make broken-links` (this file not flagged). ## AI disclosure Prepared with assistance from Claude Code; see the `Co-Authored-By` trailer on the commit. --- <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 19:12:50 -04:00
yindo closed this issue 2026-06-05 19:12:50 -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#4125
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?