docs: surface Valkey support on the external Redis page#3686
Open
Mukil Loganathan (langchain-infra) wants to merge 2 commits intomainfrom
Open
docs: surface Valkey support on the external Redis page#3686Mukil Loganathan (langchain-infra) wants to merge 2 commits intomainfrom
Mukil Loganathan (langchain-infra) wants to merge 2 commits intomainfrom
Conversation
Valkey has been an officially supported drop-in replacement for Redis since LangSmith Self-Hosted v0.14, but the only reference on the external Redis page was a buried inline note in the Requirements list. - Update the page title and sidebar title to "Connect to an external Redis or Valkey database" so it shows up in nav and search. - Add a dedicated intro paragraph calling out Valkey as a drop-in replacement, linking to the Requirements section. - Promote the supported versions line to a first-class bullet (Redis >= 5, or Valkey 8) instead of a "Note:" aside. - Annotate ElastiCache and Memorystore as Redis-or-Valkey. Azure intentionally unchanged — no Valkey variant exists there.
Contributor
|
Thanks for opening a docs PR, Mukil Loganathan (@langchain-infra)! When it's ready for review, please add the relevant reviewers:
|
Cross-links to the external Redis page weren't enough — a reader scanning the AWS or GCP self-hosted pages for their infra checklist could miss that ElastiCache for Valkey and Memorystore for Valkey are supported. - AWS self-hosted: card subtitle now reads "Redis or Valkey for caching"; ElastiCache reference-architecture bullet lists Redis or Valkey and spells out the supported versions (Redis >= 5, Valkey 8). - GCP self-hosted: same treatment for the Memorystore card and bullet, linking to the Memorystore for Valkey product page. - Self-hosted overview: datastore table row renamed to "Redis / Valkey", adds a sentence noting Valkey is a drop-in replacement, and updates the link label to "Connect to external Redis or Valkey". Azure intentionally unchanged — no Azure managed Valkey offering.
Contributor
|
Mintlify preview branch generated: Site preview: https://langchain-5e9cc07a-preview-docsva-1776908745-0c598b9.mintlify.app Changed documentation pages (preview deep links): |
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
1 participant
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.
Summary
Valkey has been officially supported as a drop-in replacement for Redis since LangSmith Self-Hosted v0.14 (see
self-hosted-changelog.mdx), but it was barely visible in the self-host docs — mentioned only as a buriedNote:bullet on the external Redis page, and not at all on the per-cloud or overview pages.Changes
src/langsmith/self-host-external-redis.mdxNote:aside.src/langsmith/aws-self-hosted.mdxsrc/langsmith/gcp-self-hosted.mdxsrc/langsmith/self-hosted.mdxScope notes
kubernetes.mdxintentionally unchanged — its Redis mentions are generic architecture references, not provider/version guidance.Disclosure: drafted with Claude Code assistance.
Test plan
make lint_prosepasses on all four edited files (verified locally)#amazon-elasticache,#google-cloud-memorystore,#azure-cache-for-redis,#iam-authentication,#requirements,#redis) still resolve