Every release from 08.01.0102 to 18.00.0004 is affected. An application that builds IN lists from user input can be crashed, or left running on a corrupted heap.
Redict is deprecated: 7.3.6 is the final release and the author advises Valkey
EditorialBy TrustList Editorial
The copyleft Redis fork announced on 17 November 2026 that it will get no further releases; its author recommends moving to Valkey and says to avoid returning to Redis.
About Redict is deprecated: 7.3.6 is the final release and the author advises Valkey
Redict is deprecated: 7.3.6 is the final release and the author advises Valkey
17 November 2026: Redict, a copyleft fork of Redis, has been declared deprecated by its author, Drew DeVault, in a post on the project's website. Version 7.3.6 is the final release. Anyone who runs Redict should plan a move to another key-value server.
Not yet independently verified. This is a post on the project's own website, written by its author; we have not checked its claims about licences or about Redis. The post does not say whether security fixes will be issued for 7.3.6 or when packages will leave distributions. The advice to switch is the author's, and the migration steps given are only for package and container installs. We will update this when it can be confirmed, and remove this note.
Why the project is stopping
The post says Redict was started to rally the people who left Redis behind around a copyleft licence, as protection against a future licence change by the vendor. It says that, with the success of the Valkey project and Redis returning to a copyleft licence, Redict was not able to build a sustainable community. The author thanks contributors and users and signs off by saying the project had a good run.
The recommended destination
The author recommends that Redict users switch to Valkey. It notes that Valkey uses a permissive licence, which the author argues gives it better long-term prospects. It advises against going back to Redis, even though Redis is open source and copyleft again, because Redis uses a contributor licence agreement, which the author says would make another licence change easier. That is the author's opinion, and a team choosing a replacement should weigh licence, support and hosting options for itself.
How to switch, as described by the author
According to the post, switching is straightforward. For installs from a package manager, install the Valkey package and move the configuration file from /etc/redict.conf to /etc/valkey.conf. For containers, pull the Valkey container instead of the Redict one and make sure it runs with the appropriate configuration file.
The post does not describe moving data, replication or clusters, so those need their own plan. Before changing anything in production, take a backup of your data files, read the Valkey documentation on compatibility with the Redis version your Redict build tracks, and rehearse the change on a copy.
What teams should do
Start with an inventory of where Redict runs: servers, container images, Helm charts, compose files and infrastructure code. Search for the redict package name and the redict image reference in your repositories, because it is easy to forget a cache that has run quietly for years.
Next, decide the date. A project with no further releases is unlikely to receive fixes for new vulnerabilities from its maintainers, so the safer course is to schedule the move rather than wait for a problem. If you depend on a distribution package, check how long your distribution plans to keep shipping it, since that is not covered in the post.
Test your clients against the replacement, including any modules, scripts and configuration directives you use, and check monitoring dashboards and alerts that refer to the old service name. Then migrate a non-critical instance first, keep the old one available for rollback, and retire it once the new one has run cleanly under real load.
Our database software category lists database products to compare.
Who needs to act
This mainly matters to teams that run their own Redict servers. Applications that use Redis-compatible clients usually connect the same way to Valkey, but each team should confirm that on its own workload.
Sources
- Redict: Redict is deprecated, 17 November 2026
Categories & features
TrustList Weekly
The week in software and IT, in one email
The news that matters to buyers, new rankings and our own research. Every Thursday, free, and easy to leave.
You may be interested in
The project had planned an October release. Between eight and ten features, including SQL/PGQ graph queries, were pulled from the branch during beta and move to PostgreSQL 20.
Supabase announced on 2 October 2026 that it is acquiring Turso, the company behind libSQL and a hosted SQLite database. Both products continue: Supabase stays on Postgres and Turso on SQLite. No price was stated.
An attacker used a compromised GitHub account and leaked credentials for four weeks, copying customer contacts, contract terms, SQL editor text and encrypted API keys. PingCAP says the databases themselves were not reached.
Packages for those minor releases, including PostgreSQL 18, move to the YUM archive and get no further updates; servers on RHEL, Rocky Linux or AlmaLinux 10.0 or 9.6 should move to a newer minor release.
From 28 September 2026 Cloud SQL’s Viewer, Reader and legacy Viewer roles no longer carry the export permission, so exports using them fail. Cloud Service Mesh’s ISTIOD control planes on GKE are deprecated, with support ending on 1 March 2028.
One of the four high-severity bugs let workspace users read Kubernetes Secrets from other namespaces; GitLab.com is already patched and Dedicated customers need do nothing.
On 10 November 2026 .NET 8 and 9 left support, Python 3.10 went on 1 October and PHP 8.2 follows on 31 December. A method for finding what you run, reading each policy, and acting with months to spare.
More on TrustList
Everything here links back to the same verified catalogue. Pick your next stop.
- More DataBaseThe ranking for this subject
- CompaniesAgencies, consultancies and IT service providers, ranked by verified reviews.
- ProductsSoftware and SaaS with pricing, features, integrations and alternatives.
- AwardsAnnual recognition decided by verified reviews and an independent jury.
- LaunchesNew products and releases, voted up by the community every day.
- AI ModelsBenchmark scores and community ratings for every major model.
- RequestsBuyers describe what they need; vendors respond directly.
- PeopleReviewers, authors and makers with public profiles.
- ComparePut up to four listings side by side before you shortlist.