v3.2.0

Features

• truncate large/long debug output arguments (#523) (cf18554)

v3.1.4

We mistakenly used Object.assign to replace lodash.assign in v3.1.3, which is not supported
by the old Node.js version (0.10.x). This change was a BC change and shouldn't happen without changing
the major version, so we added lodash.assign back.

We apologize for any inconvenience.

❤️

v3.1.3

Bug Fixes

• allow convertObjectToArray to handle objects with no prototype (#507) (8e17920)

v3.1.2

Bug Fixes

• stop mutating the arguments when calling multi (#480) (a380030)

v3.1.1: Hi, Node.js v8.0.0

In this version, we added Node.js v8 into our test matrix on Travis CI.

Bug Fixes

• show error name in the error stack for Node.js 8 (a628aa7)

v3.1.0

Bug Fixes

• non-owned properties cause empty args for mset & hmset (#469) (e7b6352)

Features

• cluster: add option to control timeout on cluster slots refresh (#475) (493d095)

v3.0.0

Features

• pipeline: add #length to get the command count (a6060cb), closes #461
• sentinel: allow connection to IPv6-only sentinels (#463) (a389f3c)

v3.0.0-2

Bug Fixes

• restore the default connectTimeout to 10000 (dc8256e)

v3.0.0-1

Features

• add debug logs for resolved sentinel nodes (8f3d3f7)
• report error on Sentinel connection refused (#445) (#446) (286a5bc)
• set default port of sentinels to 26379. (#441) (539fe41)

BREAKING CHANGES

• The default port of sentinels are now 26379 instead of 6379. This shouldn't break your app in most case since few setups has the sentinel server running on 6379, but if it's your case and the port isn't set explicitly, please go to update it.

v3.0.0-0

This is a performance-focused release. We finially switch to the new version of JavaScript parser and drop the support for hiredis (Thanks to the lovely community!).
Also, we switch to denque to improve the queueing performance.

Let us know if there's any issue when using this pre-release.

Other Changes

• increase the default reconnection interval (c5fefb7), closes #414

BREAKING CHANGES

• Although the interface doesn't change after upgrading the js parser, there may be still some potential internal differences that may break the applications which rely on them. Also, force a major version bump emphasizes the dropping of the hiredis.