Redis 5.0 release notes

Upgrade urgency levels:

LOW: No need to upgrade unless there are new features you want to use.
MODERATE: Program an upgrade of the server, but it’s not urgent.
HIGH: There is a critical bug that may affect a subset of users. Upgrade!
CRITICAL: There is a critical bug affecting MOST USERS. Upgrade ASAP.
SECURITY: There are security fixes in the release.

Redis 5.0.7 Released Tue Nov 19 17:52:44 CET 2019

Upgrade urgency HIGH: many issues fixed, some may have an impact.

Hi all, Redis 5.0.7 fixes a number of bugs, none is very critical, however
there are a few that may have an impact. It’s a good idea to upgrade.
There are fixes in the area of replication from modules commands and
callbacks, AOF fsync (non critical issue), memory leaks (very rare and small),
streams beahvior (non critical), and a potential crash in commands
processing multiple keys at the same time that is there for years, and happens
very rarely, but is not impossible to trigger.

The following is the list of commits in this release.

antirez in commit 4d2a31ae:
Test: fix implementation-dependent test after code change.
1 file changed, 2 insertions(+), 2 deletions(-)

Oran Agra in commit 9f63fc98:
RED-31295 – redis: avoid race between dlopen and thread creation
2 files changed, 17 insertions(+)

antirez in commit 1a9e70c1:
Cluster: fix memory leak of cached master.
2 files changed, 9 insertions(+), 4 deletions(-)

Guy Benoish in commit 69b1b5be:
Fix usage of server.stream_node_max_*
1 file changed, 3 insertions(+), 3 deletions(-)