docs(redis): clarify compatibility scope#724
Merged
CahidArda merged 1 commit intoJul 10, 2026
Merged
Conversation
CahidArda
approved these changes
Jul 10, 2026
CahidArda
left a comment
CahidArda
left a comment
Contributor
There was a problem hiding this comment.
Thanks for the contribution!
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
2 participants
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.
Closes #632
Summary
Clarifies that the Redis compatibility page describes Upstash Redis API-level command support, not complete TypeScript SDK helper coverage.
What changed
@upstash/redishelpersWhy
ZRANGESTOREis listed on the Redis compatibility page, but there is no corresponding TypeScript SDK command doc. The compatibility page links to Redis command docs and appears to describe service/API compatibility, so clarifying the scope is safer than adding a command page for an SDK method that may not exist.