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 #2676] [MERGED] fix: link langchain-tavily to reference docs instead of PyPI #2657

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

📋 Pull Request Information

Original PR: https://github.com/langchain-ai/docs/pull/2676
Author: @mdrxy
Created: 2/17/2026
Status: ✅ Merged
Merged: 2/17/2026
Merged by: @mdrxy

Base: main ← Head: mdrxy/tavily-refs

📝 Commits (3)

  • 75b33c9 fix: link langchain-tavily to reference docs instead of PyPI
  • 227616b Merge branch 'main' into mdrxy/tavily-refs
  • 73346ca .

📊 Changes

2 files changed (+14 additions, -4 deletions)

View changed files

📝 pipeline/tools/partner_pkg_table.py (+13 -3)
📝 src/oss/python/integrations/providers/overview.mdx (+1 -1)

📄 Description

  • Fix langchain-tavily package link on the integrations overview page pointing to PyPI instead of the LangChain reference docs
  • Update partner_pkg_table.py to check for existing reference docs for third-party packages, so any external package with hosted reference docs gets linked correctly
  • Regenerate overview.mdx with the fix applied

Details

The partner package table generator (partner_pkg_table.py) only linked to reference.langchain.com for packages in the langchain-ai GitHub org. Third-party packages always fell back to PyPI links, even when reference docs existed (e.g., langchain-tavily from tavily-ai/langchain-tavily has docs at reference/python/docs/integrations/langchain_tavily.md).

The fix adds a check for whether a reference doc file exists at reference/python/docs/integrations/{package_name}.md before falling back to the PyPI URL. This is forward-compatible — any future third-party package that gets reference docs will automatically be linked correctly.

🔄 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/2676 **Author:** [@mdrxy](https://github.com/mdrxy) **Created:** 2/17/2026 **Status:** ✅ Merged **Merged:** 2/17/2026 **Merged by:** [@mdrxy](https://github.com/mdrxy) **Base:** `main` ← **Head:** `mdrxy/tavily-refs` --- ### 📝 Commits (3) - [`75b33c9`](https://github.com/langchain-ai/docs/commit/75b33c92b658496247e0860671cb508f589e2b7e) fix: link `langchain-tavily` to reference docs instead of PyPI - [`227616b`](https://github.com/langchain-ai/docs/commit/227616ba04cf87eb6dd6f8bdb4acbe829fb3d2c3) Merge branch 'main' into mdrxy/tavily-refs - [`73346ca`](https://github.com/langchain-ai/docs/commit/73346ca60d33efeb5ea8d46fe455715e2651df1e) . ### 📊 Changes **2 files changed** (+14 additions, -4 deletions) <details> <summary>View changed files</summary> 📝 `pipeline/tools/partner_pkg_table.py` (+13 -3) 📝 `src/oss/python/integrations/providers/overview.mdx` (+1 -1) </details> ### 📄 Description - Fix `langchain-tavily` package link on the integrations overview page pointing to PyPI instead of the LangChain reference docs - Update `partner_pkg_table.py` to check for existing reference docs for third-party packages, so any external package with hosted reference docs gets linked correctly - Regenerate `overview.mdx` with the fix applied ## Details The partner package table generator (`partner_pkg_table.py`) only linked to `reference.langchain.com` for packages in the `langchain-ai` GitHub org. Third-party packages always fell back to PyPI links, even when reference docs existed (e.g., `langchain-tavily` from `tavily-ai/langchain-tavily` has docs at `reference/python/docs/integrations/langchain_tavily.md`). The fix adds a check for whether a reference doc file exists at `reference/python/docs/integrations/{package_name}.md` before falling back to the PyPI URL. This is forward-compatible — any future third-party package that gets reference docs will automatically be linked correctly. --- <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:38 -05:00
yindo closed this issue 2026-02-17 17:23:38 -05:00
yindo changed title from [PR #2676] fix: link `langchain-tavily` to reference docs instead of PyPI to [PR #2676] [MERGED] fix: link `langchain-tavily` to reference docs instead of PyPI 2026-06-05 18:19:54 -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#2657
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?