-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
update web-vault to v2024.5.0 #160
Conversation
Ah nice, lets test it out. That way we have somewhere to track missing features and also can note if someone starts working on it. |
@stefan0xC i totally forgot this one, sorry. |
Seems there is a DUO issues with that version. |
I have not really looked at this release yet. Just noticed an issue with getting billing metadata (which we have not implemented), so I've set it to bw_web_builds/patches/v2024.4.2.patch Lines 33 to 40 in 916c108
|
Uch, on v2024.5.0 now haha. |
I've updated the web-vault to the newest release. Regarding testing I think that we might want to add |
Yea, that would be useful indeed. |
Thanks @stefan0xC, I implemented this web-vault in my latest PR to update the crates and Rust :). |
New web-vault release: web-v2024.4.1
Note
I've skipped
v2024.4.0
because it only removed the banner informing users about the layout change. The banner was replaced by one that shows a message if there are unassigned messages (bitwarden/clients#8655). But for that to work we'd need to provide the/api/ciphers/has-unassigned-ciphers
endpoint (bitwarden/server#3967) in vaultwarden. (This feature is currently behind theUnassignedItemsBanner
flag.)