Change:
<ins> { lib, stdenv, fetchFromGitHub, lua, jemalloc, pkg-config , tcl, which, ps, getconf , withSystemd ? lib.meta.availableOn stdenv.hostPlatform systemd, systemd # dependency ordering is broken at the moment when building with openssl , tlsSupport ? !stdenv.hostPlatform.isStatic, openssl # Using system jemalloc fixes cross-compilation and various setups. # However the experimental 'active defragmentation' feature of valkey requires # their custom patched version of jemalloc. , useSystemJemalloc ? true }: stdenv.mkDerivation (finalAttrs: { pname = "valkey"; version = "7.2.5"; src = fetchFromGitHub { owner = "valkey-io"; repo = "valkey"; rev = finalAttrs.version; hash = "sha256-nDAQbxlSBXKSJqZgvElsrZeDnHw4A4eA8f9ecXdx0/U="; }; patches = lib.optional useSystemJemalloc ./use_system_jemalloc.patch; nativeBuildInputs = [ pkg-config ]; buildInputs = [ lua ] ++ lib.optional useSystemJemalloc jemalloc ++ lib.optional withSystemd systemd ++ lib.optional tlsSupport openssl; preBuild = lib.optionalString stdenv.isDarwin '' substituteInPlace src/Makefile --replace-fail "-flto" "" ''; # More cross-compiling fixes. makeFlags = [ "PREFIX=${placeholder "out"}" ] ++ lib.optionals (stdenv.buildPlatform != stdenv.hostPlatform) [ "AR=${stdenv.cc.targetPrefix}ar" "RANLIB=${stdenv.cc.targetPrefix}ranlib" ] ++ lib.optionals withSystemd [ "USE_SYSTEMD=yes" ] ++ lib.optionals tlsSupport [ "BUILD_TLS=yes" ]; enableParallelBuilding = true; hardeningEnable = lib.optionals (!stdenv.isDarwin) [ "pie" ]; env.NIX_CFLAGS_COMPILE = toString (lib.optionals stdenv.cc.isClang [ "-std=c11" ]); # darwin currently lacks a pure `pgrep` which is extensively used here doCheck = !stdenv.isDarwin; nativeCheckInputs = [ which tcl ps ] ++ lib.optionals stdenv.hostPlatform.isStatic [ getconf ]; checkPhase = '' runHook preCheck # disable test "Connect multiple replicas at the same time": even # upstream find this test too timing-sensitive substituteInPlace tests/integration/replication.tcl  --replace-fail 'foreach mdl {no yes}' 'foreach mdl {}' substituteInPlace tests/support/server.tcl  --replace-fail 'exec /usr/bin/env' 'exec env' sed -i '/^proc wait_load_handlers_disconnected/{n ; s/wait_for_condition 50 100/wait_for_condition 50 500/; }'  tests/support/util.tcl ./runtest  --no-latency  --timeout 2000  --clients $NIX_BUILD_CORES  --tags -leaks  --skipunit integration/failover # flaky and slow runHook postCheck ''; meta = with lib; { homepage = "https://valkey.io/"; description = "A high-performance data structure server that primarily serves key/value workloads"; license = licenses.bsd3; platforms = platforms.all; maintainers = with maintainers; [ rucadi ]; changelog = "https://github.com/valkey-io/valkey/releases/tag/${finalAttrs.version}"; mainProgram = "valkey-cli"; }; }) </ins>

Discussion:
Project description A little while ago Redis went closed source, so a community fork of Redis was launched: valkey. A release is expected soon. Although the name in the README says "PlaceholderKV" it is called "valkey": Metadata homepage URL: source URL: license: bsd platforms: linux Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Probably it makes sense to wait until the first release
I would prefer to switch the package name now, so I don't forget about it later. I wouldn't want to accidentally continue using redis.
The current "releases" in the repo that should be used are still redis with redis commands, instead of "initing" this package as unstable, I would prefer to just wait until they make the release with the naming change in my opinion. Still, creating the valkey package is trivial since it is just a copy of the redis one.