Two questions at once: the version and the licence
Redis changed licence to RSALv2 and SSPLv1, adding AGPLv3 from Redis 8. Teams on an older Redis line now face a version decision and a licensing decision in the same conversation.
Challenge
The licence change and the end-of-life calendar landed together. Staying put means an unpatched version; moving forward means accepting the new licence terms or migrating to a fork -- and those are legal and engineering decisions with different owners.
Environment
Redis 7.0 or earlier in production, past community end of life, under the pre-change licence terms.
Approach
OSSeva patches the Redis version already running under its existing licence terms, so the licensing decision and the security deadline stop being the same deadline.
What this delivers
A patched Redis on the current terms, with the licence question separated from the CVE question.