Add missing integrations to the Python and TypeScript landing pages - #5139
Merged
Conversation
Each SDK landing page lists every entry in the IntegrationsGrid data for that SDK, including the ones that link off-site. Two entries were added to integrations-data.json without a matching bullet: - Langfuse (Python), added in #5086 - LangSmith (TypeScript), which also has a local guide and a sidebars.js entry Go, Java, and Ruby were already in sync.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
📖 Docs PR preview links
|
Contributor
There was a problem hiding this comment.
Pull request overview
Adds missing integration links so SDK landing pages match the integrations grid.
Changes:
- Adds Langfuse to the Python integrations list.
- Adds LangSmith to the TypeScript integrations list.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
docs/develop/python/index.mdx |
Adds the Langfuse integration link. |
docs/develop/typescript/index.mdx |
Adds the local LangSmith guide link. |
💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Contributor
|
Created #5144 to track the larger problem where the SDK landing pages duplicate the sidebar, but with no system to keep them in sync |
Duncanma
enabled auto-merge (squash)
August 19, 2026 16:32
Duncanma
approved these changes
Aug 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds two integration bullets that were missing from SDK landing pages:
/develop/python— added tointegrations-data.jsonin Add Langfuse Python integration card #5086, but the landing-page bullet was never added/develop/typescript— in the grid data andsidebars.jswith a local guide atdocs/develop/typescript/integrations/langsmith.mdx, but missing from the landing pageWhy
Each SDK landing page lists every
integrations-data.jsonentry for that SDK. I checked whether these omissions were deliberate, and they don't appear to be:sidebars.js" rule — Fix Python integrations list on develop landing page #5133 gave that as the rationale, butsidebars.jshas only the 7 local Python pages while the list has 12. The actual convention is "every grid entry for this SDK."sdk: "Python"/"Agent observability", the same shape as LangSmith and Braintrust, both already listed.Verification
I diffed all five SDK landing pages against
integrations-data.json. Go, Java, and Ruby were already in sync; Python and TypeScript each had one gap, both fixed here. All five now match.Ordering follows the grid's
localeComparesort, soLangfusesorts beforeLangGraph.The
sdk: nullentries (Datadog, Grafana Cloud, ClickStack, New Relic, SigNoz, Vantage, Prometheus) are Cloud metrics/cost integrations with no SDK binding, and are correctly absent from SDK landing pages.Checked locally:
yarn build,vale --config .vale-ci.inion both edited files (0 errors/warnings),yarn check:orphans,yarn lint:mermaid,bin/check-redirects-for-moved-pages.js.Follow-up worth considering
This hand-maintained list duplicates
integrations-data.jsonand has now drifted three times in eight days (#5133, and both gaps here). Options: render<IntegrationsGrid defaultSdks={["Python"]} />on the landing pages instead of hardcoded bullets, or add ayarn check:integrationsscript alongside the existingcheck:metrics/check:orphans. The check script is lower-risk — it keeps the current page design and just fails CI on drift. Happy to open that separately.┆Attachments: EDU-6986 Add missing integrations to the Python and TypeScript landing pages