Redict 7.3.1 is now available and includes important security updates. You may download the release on Codeberg, or update your official container images via registry.redict.io.
Redict 7.3.1 includes fixes for the following security vulnerabilities:
No other changes are included in this release.
The SHA-256 checksum of the Redict 7.3.1 release tarball is
6dbe80d28503a9252048ab81856efcfec109cdf3f924e840411c30237cf8f634.
Please be advised that Redict version 7.3.1 is scheduled for release on October 1st and includes changes which address the following vulnerabilities (currently under embargo):
Users are encouraged to upgrade their Redict installation urgently once the release is available on October 1st.
The Redict community is pleased to announce the release of Redict 7.3.0, the first stable version of our copyleft fork of Redis® OSS 7.2.4.1 You can download the release on Codeberg, or download one of our official container images from registry.redict.io.
We have written comprehensive documentation detailing our compatibility with Redis® OSS 7.2.4, which also provides detailed documentation for various migration scenarios, such as for users of the official Redis® containers on Docker Hub, downstream package maintainers, and so on.
...The initial release candidate for Redict’s first general release, 7.3.0-rc1, is now available for download and testing. You can find the release on Codeberg:
Redict 7.3.0-rc1
Update: 7.3.0-rc2 is now available, with two minor changes from rc1:
Redict 7.3.0-rc2
First time here? Redict is an independent fork of Redis®* OSS 7.2.4 licensed under the Lesser GNU General Public license (LGPL-3.0-only). Redict is not affiliated with Redis®. See the announcement for more details.
The intended audience for this release is those who can build Redict from source and test it for compatibility with their existing Redis®* databases, as well as provide feedback generally on the release. As such, users of this release should be relatively sophisticated, expert-level users, rather than a general audience.
...Like many of you, I was disappointed when I learned that Redis®1 was changing to a non-free licensing model. This is a betrayal of the free software community, but perhaps not an entirely surprising one. Forks are likely to start appearing in the coming days, and today, I would like to offer Redict to you as a possible future home for your needs, and present its trade-offs as compared to the other forks you’re likely to be choosing from soon.
...