Version 4.5.6

[4.5.6] — 2026-06-02

Changed

• Redis → Valkey — Cipi now provisions Valkey (the BSD-licensed, Redis-compatible fork shipped in Ubuntu 24.04 Universe as valkey + valkey-tools) instead of redis-server. Valkey speaks the same RESP protocol on the same port (127.0.0.1:6379) and honours the same requirepass/bind directives, so apps need zero changes: the phpredis extension and existing REDIS_* .env values keep working as-is. setup.sh installs and configures Valkey (/etc/valkey/valkey.conf, service valkey-server); cipi service … manages valkey-server (with redis-server/redis/valkey accepted as aliases); credentials live under valkey_user/valkey_password in server.json (legacy redis_* keys are still read as a fallback). cipi reset valkey-password replaces cipi reset redis-password (the old name stays as an alias).
• Migration 4.5.6 — automatic Redis → Valkey switch for existing servers — on cipi self-update, servers still running redis-server are migrated to Valkey reusing the current password (recovered from server.json or /etc/redis/redis.conf), so no app .env needs editing. It first verifies the valkey package is installable (so a server that can't obtain it keeps its working cache backend untouched), preserves the dataset (forces an RDB SAVE and snapshots dump.rdb/AOF, restored into Valkey's data dir after install — Valkey reads the Redis 7.2 RDB/AOF format, so cache/sessions/queued jobs survive), then stops and purges redis-server (avoiding any apt Conflicts/Replaces ambiguity between the two packages) before installing and configuring Valkey on the same port with the same requirepass/bind, and rewrites server.json (redis_* → valkey_*) and the unattended-upgrades blacklist. If the install fails it restores redis-server with the saved password, so the server is never left without a cache backend; otherwise rollback is a plain apt install redis-server (the password lives in server.json). The migration is idempotent and safe to re-run.