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 #3686] [MERGED] docs: surface Valkey support on the external Redis page #3719

New Issue
Closed
opened 2026-06-05 18:52:55 -04:00 by yindo · 0 comments
yindo commented 2026-06-05 18:52:55 -04:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/langchain-ai/docs/pull/3686
Author: @langchain-infra
Created: 4/22/2026
Status: ✅ Merged
Merged: 4/23/2026
Merged by: @langchain-infra

Base: main ← Head: docs/valkey-external-redis-page

📝 Commits (2)

  • 73a33c2 docs: surface Valkey support on the external Redis page
  • 15c5689 docs: mention Valkey on AWS/GCP/self-hosted overview pages

📊 Changes

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

View changed files

📝 src/langsmith/aws-self-hosted.mdx (+2 -2)
📝 src/langsmith/gcp-self-hosted.mdx (+2 -2)
📝 src/langsmith/self-host-external-redis.mdx (+9 -7)
📝 src/langsmith/self-hosted.mdx (+1 -1)

📄 Description

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 buried Note: bullet on the external Redis page, and not at all on the per-cloud or overview pages.

Changes

src/langsmith/self-host-external-redis.mdx

  • Title + sidebar title renamed to "Connect to an external Redis or Valkey database". URL slug unchanged, so cross-links still resolve.
  • Added intro paragraph calling out Valkey as a drop-in replacement and linking to the Requirements section.
  • Promoted the supported-versions line to a first-class bullet (Redis >= 5, or Valkey 8) instead of a Note: aside.
  • Annotated ElastiCache and Memorystore as "Redis or Valkey".

src/langsmith/aws-self-hosted.mdx

  • ElastiCache card: "Redis for caching" → "Redis or Valkey for caching".
  • Reference-architecture bullet: switched to the top-level ElastiCache product page and spelled out the supported versions (Redis >= 5, Valkey 8).

src/langsmith/gcp-self-hosted.mdx

  • Memorystore card: same subtitle update.
  • Reference-architecture bullet: now links both the Memorystore for Redis and Memorystore for Valkey product pages.

src/langsmith/self-hosted.mdx

  • Datastore table row renamed "Redis" → "Redis / Valkey" (anchor id="redis" preserved for backward-compat).
  • Added a sentence noting Valkey is officially supported as a drop-in replacement.
  • Link label updated to "Connect to external Redis or Valkey".

Scope notes

  • Azure pages intentionally unchanged — there is no Azure managed Valkey service.
  • kubernetes.mdx intentionally unchanged — its Redis mentions are generic architecture references, not provider/version guidance.

Disclosure: drafted with Claude Code assistance.

Test plan

  • make lint_prose passes on all four edited files (verified locally)
  • Preview build shows the new title, the updated cards on the AWS and GCP pages, and the "Redis / Valkey" row on the self-hosted overview
  • Existing anchor links into the external Redis page (#amazon-elasticache, #google-cloud-memorystore, #azure-cache-for-redis, #iam-authentication, #requirements, #redis) still resolve

🔄 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/3686 **Author:** [@langchain-infra](https://github.com/langchain-infra) **Created:** 4/22/2026 **Status:** ✅ Merged **Merged:** 4/23/2026 **Merged by:** [@langchain-infra](https://github.com/langchain-infra) **Base:** `main` ← **Head:** `docs/valkey-external-redis-page` --- ### 📝 Commits (2) - [`73a33c2`](https://github.com/langchain-ai/docs/commit/73a33c2b673d33ed83594769c289416eda5fa231) docs: surface Valkey support on the external Redis page - [`15c5689`](https://github.com/langchain-ai/docs/commit/15c56895049d1b8a5b4ccac20178027d7489f01e) docs: mention Valkey on AWS/GCP/self-hosted overview pages ### 📊 Changes **4 files changed** (+14 additions, -12 deletions) <details> <summary>View changed files</summary> 📝 `src/langsmith/aws-self-hosted.mdx` (+2 -2) 📝 `src/langsmith/gcp-self-hosted.mdx` (+2 -2) 📝 `src/langsmith/self-host-external-redis.mdx` (+9 -7) 📝 `src/langsmith/self-hosted.mdx` (+1 -1) </details> ### 📄 Description ## 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 buried `Note:` bullet on the external Redis page, and not at all on the per-cloud or overview pages. ## Changes **`src/langsmith/self-host-external-redis.mdx`** - Title + sidebar title renamed to "Connect to an external Redis or Valkey database". URL slug unchanged, so cross-links still resolve. - Added intro paragraph calling out Valkey as a drop-in replacement and linking to the Requirements section. - Promoted the supported-versions line to a first-class bullet (Redis >= 5, or Valkey 8) instead of a `Note:` aside. - Annotated ElastiCache and Memorystore as "Redis or Valkey". **`src/langsmith/aws-self-hosted.mdx`** - ElastiCache card: "Redis for caching" → "Redis or Valkey for caching". - Reference-architecture bullet: switched to the top-level ElastiCache product page and spelled out the supported versions (Redis >= 5, Valkey 8). **`src/langsmith/gcp-self-hosted.mdx`** - Memorystore card: same subtitle update. - Reference-architecture bullet: now links both the Memorystore for Redis and Memorystore for Valkey product pages. **`src/langsmith/self-hosted.mdx`** - Datastore table row renamed "Redis" → "Redis / Valkey" (anchor id="redis" preserved for backward-compat). - Added a sentence noting Valkey is officially supported as a drop-in replacement. - Link label updated to "Connect to external Redis or Valkey". ## Scope notes - Azure pages intentionally unchanged — there is no Azure managed Valkey service. - `kubernetes.mdx` intentionally unchanged — its Redis mentions are generic architecture references, not provider/version guidance. Disclosure: drafted with Claude Code assistance. ## Test plan - [ ] `make lint_prose` passes on all four edited files (verified locally) - [ ] Preview build shows the new title, the updated cards on the AWS and GCP pages, and the "Redis / Valkey" row on the self-hosted overview - [ ] Existing anchor links into the external Redis page (`#amazon-elasticache`, `#google-cloud-memorystore`, `#azure-cache-for-redis`, `#iam-authentication`, `#requirements`, `#redis`) still resolve --- <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 18:52:55 -04:00
yindo closed this issue 2026-06-05 18:52:55 -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#3719
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?