Update docker.io/redis Docker tag to v8.8.0

Share
Update docker.io/redis Docker tag to v8.8.0
Photo by Silas Köhler / Unsplash

Successfully upgraded the Docker container on the Database Host by means of Watchtower container with dependency update facilitated by Mend's Renovate Bot and on the Mastodon instance manually with Docker compose.

This MR contains the following updates:

Package Update Change
docker.io/redis minor 8.6.3-alpine8.8.0-alpine

Release Notes

redis/redis (docker.io/redis)

v8.8.0

Compare Source

This is the General Availability release of Redis 8.8 in Redis Open Source.

Major changes compared to 8.6
  • New data structure: Array (@​antirez)
  • Subkey notification for hash fields - field-level notifications
  • INCREX: a window counter rate limiter combining INCR, INCRBY, INCRBYFLOAT, bounds, and expiration (@​raffertyyu + Redis team)
  • XNACK: a new streams command - allow consumers to explicitly release pending messages
  • ZUNION, ZINTER, ZUNIONSTORE, ZINTERSTORE: new COUNT aggregator
  • JSON.SET: new FPHA argument to specify the FP type for homogeneous FP arrays
  • TS.RANGE, TS.REVRANGE, TS.MRANGE, TS.MREVRANGE: multiple aggregators in a single command
  • FT.HYBRID KNN clause: new argument to request fewer candidates per shard
  • FT.PROFILE HYBRID: profiling support for FT.HYBRID
  • Performance improvements
Binary distributions
Operating systems we test Redis 8.8 on
  • Ubuntu 22.04 (Jammy Jellyfish), 24.04 (Noble Numbat), 26.04 (Resolute Raccoon)
  • Rocky Linux 8.10, 9.7, 10.1
  • AlmaLinux 8.10, 9.7, 10.1
  • Debian 12.13 (Bookworm), Debian 13.4 (Trixie)
  • Alpine 3.23
  • macOS 14.8.4 (Sonoma), 15.7.4 (Sequoia), 26.3 (Tahoe) - for both Intel and ARM
Bug fixes (compared to 8.8-RC1)

v8.6.4

Compare Source

Update urgency: HIGH: There are critical bugs that may affect a subset of users.

Bug fixes
  • #​15175, RediSearch/RediSearch#9262 Redis fails to start on AArch64
  • #​15163 MULTI queue memory incorrect memory accounting
  • #​15115 Under-copy in the Lua debugger
  • #​15094 Cluster crash when CLIENT KILL unsubscribes SSUBSCRIBE client inside EXEC
  • #​14963 XREADGROUP: consumer replication inconsistency
  • #​14934 Client output buffer memory tracking not accounting for copy-avoided bulk string references
  • #​14970 Sentinel config injection via SENTINEL SET
  • #​14982 SCAN commands: integer overflow in COUNT parameter
  • #​15073 CLIENT TRACKING: self-overlap returning non-zero loop index
  • #​15059 Use-after-free
  • #​15037 XINFO STREAM: wrong value in the per-slot memory tracking
  • #​15034, #​15081 Issues processing corrupt RDB data
  • #​15021 HEXPIRE: overflow on fields count
  • #​14942 Fix COMMAND GETKEYS for PFMERGE with no source keys
  • #​15188 cluster-announce-ip rejecting hostnames (regression)
  • #​14667, #​14886 Potential TCP stalls/deadlocks
  • RediSearch/RediSearch#9484 Shard crash during background index scan of JSON documents with vector fields on Active-Active (CRDT) databases (MOD-15542)
  • RediSearch/RediSearch#9635 Severe latency spikes and shard unresponsiveness when EXPIRE or EXPIREAT operations run concurrently with queries on large indexes (MOD-14930)

Read more

Me on Mastodon - This link is here for verification purposes.