I suspect Redis is going to pull in the various popular Redis libraries under their umbrella and make them incompatible with Valkey. It seems like a defensive move against Valkey.

If I was in charge of any of these libraries, I would replace any mention of Redis with Valkey and move on.

Sure. You can do that. But the community needs a single standard. Open standard that all in-memory data stores like Redis, ValKey, DragonflyDB, KeyDB, Kvrocks will support. Otherwise you will end up in a vendor lock.

And what prevents valkey devs from maintaining their compatibility layer to accommodate those changes?