sendCommand on multi for all clients by @nkaradzhov in https://github.com/redis/node-redis/pull/3181sSubscribe/sUnsubscribe methods to Sentinel client by @nkaradzhov in https://github.com/redis/node-redis/pull/3178INDEXMISSING placement by @nkaradzhov in https://github.com/redis/node-redis/pull/3179@redis/client dist imports in CREATE command by @PavelPashov in https://github.com/redis/node-redis/pull/3187transformDoubleReply by @rhymincymon in https://github.com/redis/node-redis/pull/3213Node Redis now ships with first-class observability via OpenTelemetry metrics and Node.js diagnostics_channel. Initialize OpenTelemetry before creating clients (OpenTelemetry.init({ metrics: { enabled: true } })) and you can plug Redis client telemetry into your existing OTel SDK/exporter pipeline.
This enables visibility into command latency, connection lifecycle, resiliency/errors, Pub/Sub traffic, streaming behavior, and client-side caching activity. On top of metrics, diagnostics channels provide a more abstract, higher-level way to track runtime behavior through low-overhead event streams (commands, batches, connection events, maintenance notifications, pub/sub, cache, and pool wait timing), so APM tools or custom subscribers can observe the system without changing application code.
Full Changelog: https://github.com/redis/node-redis/compare/redis@5.11.0...redis@5.12.0
Fetched May 1, 2026