policy for older Redis than supported: just untested, or actively refuse to connect?

[petertseng]

I see that the README says that for redis-py library >= 6.0.0 the supported Redis version is 7.2 to current.

Now I am considering what to do in an environment where the Redis server version is older than 7.2 but I don't have the privileges to upgrade it.

I could simply stay on the 5.x library versions. This is probably okay, as long as I don't need anything from 6.x. It may feel bad to be behind, but it will ensure that the library supports the Redis version.

Or I could update to 6.x library anyway, and use it with the old and unsupported Redis version. Unofficially I have observed that this seems to work, but I understand that being unsupported means there aren't any guarantees. So it looks like the library doesn't actively refuse to connect to an older Redis server, and it's mainly that they aren't in the test matrix and we use the older versions at our own risk.

Do I have the right ideas here?

[petyaslavova]

Hi @petertseng, you're absolutely right about how the support matrix is updated. When a version is not listed as compatible, it doesn't necessarily mean it won't work — it simply means we don't actively test against it. As a result, if any issues arise with that version, especially with specific commands, we won't be addressing them.

[petertseng]

Thanks for answering the question and confirming my understanding! As far as I can tell, since my question is answered, this issue is complete.