Yeah, the problem is with clients from January or newer, and vaultwarden versions from before October.

It did lead me to discover my automatic update process wasn't actually rebooting the vaultwarden server.