We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
With the recent changes in Redis licensing from BSD-3 to dual RSALv2+SSPLv1, what will the future of ioredis support look like?
Will this come in the form of transitioning to other forked version of redis like Valkey?
The text was updated successfully, but these errors were encountered:
Where are we at - do we have a fork that is maintained and what we have moved on with?
It seems this is not maintained. There is 200+ issues not resolved, and the last release was 1 year ago.
Sorry, something went wrong.
Just to avoid confusion: The ioredis library is MIT licensed and its OSS license is not impacted by the recent Redis server license change.
@thanh17 @billnbell2 This question was extensively covered here #1870 (comment) Since then, we released 5.4 maintenance release and executed the strategy outlined before. All official Redis clients are MIT-licensed.
No branches or pull requests
With the recent changes in Redis licensing from BSD-3 to dual RSALv2+SSPLv1, what will the future of ioredis support look like?
Will this come in the form of transitioning to other forked version of redis like Valkey?
The text was updated successfully, but these errors were encountered: