Redis

Redis

Database

Redis 8.10 is the newest actively maintained release, currently at patch 8.10.1. 9 of 12 tracked cycles remain supported. The next cycle scheduled to reach end-of-life is 8.0, on December 1, 2026.

Latest version

8.10.1

Aug 17, 2026

Actively maintained cycles

9

of 12 tracked

Total cycles tracked

12

since Oct 17, 2018

Support pattern

How Redis has behaved across the cycles tracked here, rather than what its policy documents state. Useful for judging how much runway a version is likely to have before you commit to it.

Typical support window

52 mo (~4.3 years)

median of 8 completed cycles

New cycle roughly every

9 months

median gap between releases

Compared with database

+33 mo

longer than the database median

Next end of life

83 days

Redis 8.0

Support windows are getting longer: the most recent cycles run about 28 months longer than the earlier ones.

Computed from release and end-of-life dates tracked for Redis. Medians are used rather than averages so one unusually short or long release does not skew the figure. Cycles with no recorded end-of-life date are excluded from the support window.

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.

Actively maintained

The newest minor version(s) in a major line. It receives new features and every class of fix.

Security support only

Once superseded by a newer minor, a version keeps receiving fixes for security vulnerabilities and critical bugs, but no new features.

End of life

The version stops receiving any patches, even for newly discovered vulnerabilities.

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

Release lifecycle

Actively maintainedSecurity support onlyEnd of life
Today
8.10Latest
8.10.1 · Aug 17, 2026
8.8
8.8.2 · Aug 17, 2026
8.6
8.6.6 · Aug 17, 2026
8.4
8.4.6 · Aug 17, 2026
8.2
8.2.9 · Aug 17, 2026
8.0
8.0.6 · Feb 22, 2026
7.4
7.4.11 · Aug 17, 2026
7.2
7.2.16 · Aug 17, 2026
7.0
EOL Jul 29, 2024
6.2
6.2.24 · Aug 17, 2026
6.0
EOL May 31, 2022
5.0
EOL Apr 27, 2022
20192020202120222023202420252026

Get an email when Redis ships a release, announces an end-of-life date, or moves a date it already announced.

Get Redis alerts