Redis: Weekly Recap - Security Releases and Memory Control

Redis shipped coordinated security patches across five branches centered on cluster bus authentication and transaction access control. The week also added Bless no-evict protection and append-only replay estimates alongside stream and expiry reliability fixes.

Duration: PT3M12S

Episode overview

This episode is a short developer briefing from Redis.

It explains recent repository work in plain language.

  • Show: Redis
  • Published: 2026-09-21T09:38:15Z
  • Audio duration: PT3M12S

Transcript excerpt

This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.

Hello, and welcome to the Redis weekly recap for September 14th to September 21st, 2026.

We tracked 36 pull request activity items, 11 additional commits this week.

Our lead story is security. Redis shipped coordinated patch releases across five branches, from version 8.2 through 8.10, all centered on cluster and access control hardening.

First, cluster bus protection. Pull request 15722, backported in releases 15800 through 15804, makes an unauthenticated cluster bus port an explicit choice. Nodes now refuse to start in cluster mode without transport layer security for the cluster bus, unless operators explicitly disable the new cluster bus…

Second, memory control and persistence visibility. Pull request 15649 adds Bless, a new command family to mark specific keys as no-evict under memory limits. Blessed keys are never chosen as eviction victims, survive restart, replication and slot migration, and are counted in system info. Under heavy pressure,…

Third, client tooling and test hardening. Pull request 15817 makes key-size analysis in the command line interface use no-touch mode, so big-keys and key-stats scans no longer distort least-recently-used or least-frequently-used metadata.…

Nearby episodes from Redis

  1. Stream Trim Persistence Risk and Cleaner Scans
  2. Scan Command Cleanup
  3. Security Patches Ship Across Five Release Lines
  4. Data Correctness Fixes Across Streams, Sorted Sets, and Scripting
  5. Security Patches Roll Backward Across Four Release Lines
  6. Trust Boundaries Get Tighter
  7. Checksum Performance and a Version Bump Cluster
  8. Weekly Recap - Correctness Fixes and Read-Path Performance