Skip to main content

Redis 8.12.0

Release Date: November 22, 2026

Redis 8.12.0 reached general availability on November 22, 2026. The release, published on the project's 8.12 branch as Redis Open Source, brings the redis-roaring bitmap engine into the core server, adds member-level expiration for sets, and introduces a B+ tree encoding for large sorted sets.

The release notes frame the work as the set of "major changes compared to 8.10," which puts the gap at two minor lines rather than one. Operators tracking the 8.10 branch should read the note before planning an upgrade: surface area changed in commands, in encoding, and in the cluster tooling.

What Changed

  • Compressed bitmaps. redis-roaring is now integrated into Redis core, which the notes describe as lower memory use and faster bitmap operations. The integration credits Antonio Viggiano, the original author of redis-roaring.
  • BITRANGEINTARRAY. A new command, equivalent to redis-roaring's R.RANGEINTARRAY, that returns the set bit offsets inside a given range.
  • Sorted sets get a B+ tree encoding. The notes promise "substantial memory reduction for large sorted set," which is the kind of claim that only a benchmark against your own keys will settle.
  • Set member expiration. SEXPIRE, SPEXPIRE, SEXPIREAT and SPEXPIREAT set a TTL on an individual set member; STTL, SPTTL, SEXPIRETIME and SPEXPIRETIME read it back; SETPERSIST removes it.
  • BLESS. A new command that protects specified keys from eviction, aimed at deployments where a handful of hot keys must survive an allkeys-lru policy.
  • Atomic sorted-set moves. ZMOVE, BZMOVE and ZMOVEMEMBER move members between sets with source and destination conditions, covering end-of-set batch patterns.
  • Smaller additions. Count-min-sketch extensions, automatic creation of deep JSON paths, and opt-in SQ8 compression for HNSW vector indexes.
  • Cluster migration visibility. CLUSTER MIGRATION STATUS now reports progress for both the snapshot and the incremental phase of a slot migration.

Query Engine Fixes

Three changes land in the Redis query engine. FT.ALTER no longer reindexes documents it does not need to touch when a schema is extended, EXPLAINSCORE now works with FT.HYBRID, and RETURN_STRICT timeout handling is enabled for local FT.HYBRID execution.

Why It Matters

Member-level expiration is the headliner for application developers. Until now, a TTL lived on the key, so any set holding per-member state had to be reaped by application code or split across many keys. SEXPIRE moves that bookkeeping into the server, which also means replication and persistence carry it.

BLESS is the other command with operational weight. Eviction policies are blunt: either everything is a candidate or only keys with a TTL are. A way to mark specific keys as off limits answers a request that has been open in the community for years, and it does so without forcing a second instance.

Fixes in This Build

  • HOTKEYS GET reported a wrong collection-duration-ms after roughly 2^31 milliseconds (#16252).
  • HPERSIST ignored a replicated or AOF persist of a hash field that the local clock had already expired (#16219).
  • Replicas misbehaved when replication compression was enabled (#16207).
  • BITCOUNT returned wrong results on AArch64 with large dense bitmaps (#16267), a bug that matters now that the roaring code sits in core.
  • Addresses and names announced on the cluster bus were accepted without validation (#16081).
  • RedisTimeSeries no longer crashes when loading persisted compaction rules with an invalid aggregation type (MOD-20881).
  • RedisJSON's JSON.ARRINSERT no longer partially modifies an array before returning a validation error (MOD-9116).
  • RedisBloom initializes the TopK seed generator once, cutting random-seed generation from every command to a single call.

What's Next

Test this one on a copy of production data rather than a synthetic set of a million keys. The two memory claims, roaring bitmaps and the B+ tree sorted set encoding, depend on shape and cardinality, and the encoding change is the kind of thing that shows up as either a large win or no win at all. Check that client libraries and modules you depend on are current, then plan a rolling restart during a window you control. The 8.10 branch took a security patch on October 26, so clusters still sitting on 8.10.2 have a second reason to move.

Other Versions

We use cookies for ads and analytics.