-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: redis/node-redis
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: json@5.8.1
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: redis/node-redis
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: json@5.8.2
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 14 commits
- 25 files changed
- 5 contributors
Commits on Aug 13, 2025
-
Configuration menu - View commit details
-
Copy full SHA for 603fa71 - Browse repository at this point
Copy the full SHA 603fa71View commit details -
Configuration menu - View commit details
-
Copy full SHA for c0e6c78 - Browse repository at this point
Copy the full SHA c0e6c78View commit details -
Configuration menu - View commit details
-
Copy full SHA for 4e5e31d - Browse repository at this point
Copy the full SHA 4e5e31dView commit details -
Configuration menu - View commit details
-
Copy full SHA for cafdc63 - Browse repository at this point
Copy the full SHA cafdc63View commit details -
docs: Clustering sendCommand docs (#3053)
We noticed that `sendCommand()` takes different arguments for clusters vs clients, and I wanted to document the differences. I think I got it correct, but please review closely just to be sure.
Configuration menu - View commit details
-
Copy full SHA for 746e9b1 - Browse repository at this point
Copy the full SHA 746e9b1View commit details
Commits on Aug 14, 2025
-
fix: Stop erasing
ErrorReply
stack (#3050)It was very difficult to debug `ErrorReply` errors due to `error.stack` being erased. Given this restores standard JS Error behaviour, I have not added any tests.
Configuration menu - View commit details
-
Copy full SHA for 82847fb - Browse repository at this point
Copy the full SHA 82847fbView commit details -
Configuration menu - View commit details
-
Copy full SHA for fceb609 - Browse repository at this point
Copy the full SHA fceb609View commit details
Commits on Aug 18, 2025
-
fix(ts): xtrim threshold accepts string (#3058)
* fix(ts): xtrim threshold accepts string * test: check MINID with text id
Configuration menu - View commit details
-
Copy full SHA for ed6aca7 - Browse repository at this point
Copy the full SHA ed6aca7View commit details -
Configuration menu - View commit details
-
Copy full SHA for d5423b9 - Browse repository at this point
Copy the full SHA d5423b9View commit details
Commits on Aug 20, 2025
-
fix(sentinel): properly pass reconnectStrategy (#3063)
Properly pass reconnectStrategy to master/replica nodes. Before that strategies passed in the nodeClientOptions.socket object were ignored. fixes #3061
Configuration menu - View commit details
-
Copy full SHA for e347d56 - Browse repository at this point
Copy the full SHA e347d56View commit details -
Configuration menu - View commit details
-
Copy full SHA for b9a5d36 - Browse repository at this point
Copy the full SHA b9a5d36View commit details -
Configuration menu - View commit details
-
Copy full SHA for 2e66012 - Browse repository at this point
Copy the full SHA 2e66012View commit details -
Configuration menu - View commit details
-
Copy full SHA for 0a5d076 - Browse repository at this point
Copy the full SHA 0a5d076View commit details -
Configuration menu - View commit details
-
Copy full SHA for 5e575b9 - Browse repository at this point
Copy the full SHA 5e575b9View commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff json@5.8.1...json@5.8.2