Redict deprecated; 7.3.6 is final, author points users to Valkey
Redict is deprecated with 7.3.6 as the final release. What its author says about Valkey, the migration steps, and what to check first.
Redict, the copyleft fork of Redis, is deprecated, and version 7.3.6 is its final release, project founder Drew DeVault announced on November 17, 2026.
For anyone still running Redict, that means no further releases from the project, so the practical step is to plan a move off it. The announcement does not mention a security-patch window or any continued maintenance, so operators should assume 7.3.6 is the last version they will receive fixes in.
Stated reasons. DeVault wrote that he had hoped to rally the Redis diaspora around a copyleft project to guard against future license rug-pulls. With the success of Valkey and Redis's return to a copyleft license, he said, Redict "was not able to build a sustainable community."
Recommended target. The post recommends Valkey, which uses a permissive license and which DeVault says has better long-term prospects. It advises against going back to Redis. Although Redis is again open source and copyleft, DeVault says its contributor license agreement would make another relicensing possible. That is his assessment, not an established fact.
Documented migration steps. The post describes the move as straightforward. If you install from a package manager, install the valkey package and move the config file:
# mv /etc/redict.conf /etc/valkey.conf
For containers, pull the Valkey image instead and make sure it runs with the appropriate config file. The announcement gives no compatibility matrix and says nothing about data files, versions or module support.
What to check. One reader reports a gap in that guidance. In the Lobsters discussion, user legoktm said the RDB formats were incompatible when they switched to Valkey in containers, so they deleted the old dump and let Valkey start empty. They noted this was acceptable because the instance was an ephemeral cache. This is one unverified user report, and we have not tested it. Still, operators holding persistent data in Redict should not assume an existing RDB or AOF file will load. Before cutting over:
- Test loading your actual dump into the target Valkey version in staging.
- If the load fails, plan a live migration, for example replaying data through a client-side copy, rather than a file swap.
- Review your config file for Redict-specific directives, since a simple rename may not be enough.
- Check client libraries and any modules you depend on against Valkey.
Caches can simply start cold. Anything holding durable state needs a rehearsed migration.
The announcement does not say whether Redict's repository will be archived or how long packages will remain available. Check your distribution's package status for removal notices.
Comments ()