Redis

How Redis versioning, EOL & security support work

Redis follows a MAJOR.MINOR.PATCH scheme. Major versions (like the Redis 7 → 8 jump) can include breaking changes; minor versions (8.2 → 8.4 → 8.6 → 8.8, shown below) add new features within a major line; patch releases (8.6.1 → 8.6.2) are fixes only. Redis's own guidance is direct: "we strongly recommend using the latest available version" for the newest security and performance work.

This is exactly what the color-coded status next to each version in the timeline below means. Security issues go through Redis's official vulnerability disclosure process rather than being posted publicly first, and fixes ship for currently-supported versions once they're ready. That's why running a version that's already reached end-of-life is the riskiest state: a newly discovered vulnerability there will never get patched.

Sources: Redis Open Source version management, Redis Security Policy

Data sourced from endoflife.date.