On Sat 18/02/2023 09:49, aisha wrote: > On 23/01/14 09:17PM, Bjorn Ketelaars wrote: > > On Sat 14/01/2023 12:26, A Tammy wrote: > > > There can be multiple versions of the web-vault which are compatible > > > with the current version of vaultwarden, so keeping it independent makes > > > it easy to update it separately. > > > > > > Also the web-vault has had more frequent releases, not always breaking, > > > mostly bug fixes. So it would be good to have them when possible. It's > > > rare that the breakage happens but not impossible, so I wanted to get > > > more testers. > > > > > > One of the reasons why I initially made it separate was that the web > > > vault is not developed by vaultwarden themselves, more of a patching of > > > the upstream bitwarden web vault by removing branding. So I thought it > > > made more sense to keep them in separate places. > > > > > > Also didn't want to trigger a build of vaultwarden every time the web > > > vault got a new release, my build machine is slow and rust is chonky. > > > > > > Not a big difference imo. > > > > Clear, I understand your reasoning. > > > > forgot to apply this when I said I would, so now there is a new version > 2023.1.1 (patch release from 2023.1.0) > > no functionality changes, everything is working fine. > > OK?
OK bket@
