update web-vault to v2025.2.1

[stefan0xC]

New web-vault release: web-v2025.1.2

I've re-enabled the calling of the collection-managment endpoint (and also the environment-selector is not patched out anymore).

There's a new endpoint needed for email verification on signup: /identity/accounts/register/send-verification-email

{"email":"test@example.com","name":"test","receiveMarketingEmails":false}

I have not looked much into it so I'm not sure if we can implement this in a way so that Vaultwarden will be usable without enabling mails. Does a self-hosted Bitwarden server require that?

[BlackDex]

I think @dani-garcia was working on that via dani-garcia/vaultwarden#5215

[tessus]

v2025.2.0 is available ;-)

[stefan0xC]

As far as I've looked into the changes they don't seem to warrant an update for me. (I mean, I will probably do it eventually, but I don't think that we have to rush it in this case...)

[BlackDex]

@stefan0xC should we wait for the 2025.2.1 patch? Or should we just merge this one as-is?
Not sure if there are lots of changes to be done using this version or the next one.

[tessus]

Doesn't this PR require dani-garcia/vaultwarden#5215 to be merged first? Ah, I guess there won't be release until the server PR will have been merged.

[BlackDex]

Well, I'd rather test the latest version, unless there are a lot of other changes to be done first. Checking the PR 5215 with the latest is then probably better to do.

[stefan0xC]

There are a few further changes at least one of which that would require a change in the backend (to turn new device verification off) but I have not looked further into it.

[ecesarini]

It looks like that since new web-v2025.2.1 email confirmation will be the only way to create an account.
I'm checking the new bitwarden release and the whole apps/web/src/app/auth/trial-initiation/ directory has been moved in apps/web/src/app/billing/trial-initiation and some files that handle the previous create account form have been deleted.
Is it right?

[stefan0xC]

As far as I've tested the PR mentioned in #190 (comment) the registration will work just fine when mail is not configured or SIGNUPS_VERIFY=false.