Version 4.5.7

[4.5.7] — 2026-06-02

Fixed

• Valkey install used the wrong package name — setup.sh and migration 4.5.6 installed valkey, but on Ubuntu 24.04 the daemon package is valkey-server (source valkey; binaries valkey-server + valkey-tools). On servers that had already updated to 4.5.6 the switch aborted with "valkey package not available" and left redis-server running (no data touched). Since 4.5.6 has already shipped and a migration can't be re-run, setup.sh is corrected to valkey-server and migration 4.5.7 performs the full, corrected Redis → Valkey switch itself (self-contained: reuse password, preserve the RDB/AOF dataset, purge redis-server, install valkey-server + valkey-tools, restore data, rewrite server.json/blacklist). It adds extra safety nets: it auto-enables the universe component when the package isn't found (via add-apt-repository if present, otherwise by editing the deb822/legacy APT sources directly — no software-properties-common needed) and re-checks; it runs a post-start health check (PING → PONG with the password) and, if Valkey doesn't come up healthy (or can't be installed), rolls back to redis-server restoring both the saved password and the dataset, so the server is never left without a working cache backend. The dataset snapshot is kept until the switch is verified, then cleaned up. Idempotent — servers already on Valkey skip it.