Skip to content
This repository was archived by the owner on May 30, 2024. It is now read-only.

Commit 7d21185

Browse files
Releasing version 5.13.4
1 parent 9e7667c commit 7d21185

File tree

3 files changed

+6
-2
lines changed

3 files changed

+6
-2
lines changed

CHANGELOG.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,10 @@
22

33
All notable changes to the LaunchDarkly Server-Side SDK for Node.js will be documented in this file. This project adheres to [Semantic Versioning](http://semver.org).
44

5+
## [5.13.4] - 2020-08-27
6+
### Fixed:
7+
- When using the Redis integration without trying to connect to LaunchDarkly (such as when using the Relay Proxy with Redis in "daemon mode"), a flag evaluation that was done immediately after initializing the SDK client could fail due to the Redis client not having time to make its connection to Redis. This has been fixed so that it will wait for the connection to be established. This was never an issue when _not_ using daemon mode, because if the SDK did connect to LaunchDarkly then it would proceed to store the flags in Redis and would not finish initializing until it had done so. ([#193](https://github.com/launchdarkly/node-server-sdk/issues/193))
8+
59
## [5.13.3] - 2020-06-30
610
### Fixed:
711
- A bug introduced in 5.13.2 caused the output of the default logger to be formatted incorrectly.

package-lock.json

Lines changed: 1 addition & 1 deletion
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

package.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
{
22
"name": "launchdarkly-node-server-sdk",
3-
"version": "5.13.3",
3+
"version": "5.13.4",
44
"description": "LaunchDarkly Server-Side SDK for Node.js",
55
"main": "index.js",
66
"scripts": {

0 commit comments

Comments
 (0)