Skip to content

docs: link Loom retrievers to the complete installation guide - #7965

Closed
Mohammad Lareb Zafar (zlareb1) wants to merge 1 commit into
langchain-ai:mainfrom
zlareb1:docs/loom-retriever-guide-links
Closed

Mohammad Lareb Zafar (zlareb1) wants to merge 1 commit into
langchain-ai:mainfrom
zlareb1:docs/loom-retriever-guide-links

Conversation

@zlareb1

@zlareb1 Mohammad Lareb Zafar (zlareb1) commented Nov 20, 2026 •

Copy link
Copy Markdown

Why

The Loom retriever listings link to a frozen guide that omits the TypeScript framework peer from its install command. Point them to the guide that selects the inspected SDK artifacts and includes that peer.

Changes

  • Update the four Loom retriever documentation URLs in the external integration metadata.
  • Update the corresponding Python and JavaScript provider cards.
  • Update the same URLs in the two retriever download tables.

Review notes

This corrects the existing LoomKnowledgeRetriever and LoomMemoryRetriever listings. Class names, package names, capability flags, download counts, ordering and all other entries stay unchanged. No integration implementation or code example changes.

The unchanged upstream generator reproduced the four original download-table rows and rendered their replacements using the existing download counts. Scoped byte-preservation, URL-scheme and whitespace checks passed. No full download-metric refresh ran.

One anonymous read of the exact new GitHub guide URL returned HTTP 503. That check remains incomplete and was not retried. Vale is unavailable locally; local prose lint, rendered previews and the local anchor-aware link checker were not run. Hosted checks passed on this head, including Vale on changed docs, generated files, external documentation URLs and the documentation build/link check.

The linked guide selects published SDK artifacts and the supported LangChain core peer. Package metadata and selected adapter source were inspected; application execution was not repeated. An earlier run of its source PR, ClickHouse/loom#1061, failed the Go parser-cost check; that failure's cause remains unknown. No Loom CI or runtime qualification is transferred to this documentation correction.

Affiliation: Loom (ClickHouse).

Related

Follows #7947 and #7950.

Checklist

  • I read the contributing guidelines, including the language policy
  • I checked the rendered pages locally with docs dev or on the preview deployment
  • I ran every changed code example, or none changed
  • make lint_prose passes on the changed files
  • make broken-links-with-anchors passes, or no links, pages, or navigation changed
  • I updated src/docs.json navigation and redirects, or no page was added, moved, or removed

Prepared with Codex.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
@github-actions github-actions Bot added integration For docs updates for LangChain integrations javascript langchain For docs changes to LangChain oss python For content related to the Python version of LangChain projects external User is not a member of langchain-ai labels Nov 20, 2026
@zlareb1
Mohammad Lareb Zafar (zlareb1) marked this pull request as ready for review November 20, 2026 18:43
@langchain-oss-automated-triage

Copy link
Copy Markdown
Contributor

New integration listings that are neither featured by LangChain maintainers nor have at least 50,000 monthly downloads should be filed as an Integration listing issue rather than a manual PR. This pull request is being closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

external User is not a member of langchain-ai integration For docs updates for LangChain integrations javascript langchain For docs changes to LangChain oss python For content related to the Python version of LangChain projects

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant