-
Notifications
You must be signed in to change notification settings - Fork 110
update web-vault to v2025.6.2 #206
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
Conversation
|
@stefan0xC I have noticed that in 2025.6.0, a few Send options are missing. e.g. expiration date, deactivate send, copy to clipboard. I haven't been able to test 2025.6.2 yet. Has this been fixed? Btw, you first comment mentions that vaultwarden has to be updated. The delete fix was already added, thus I was wondering, whether something else was missing from vw. |
|
As far as I've looked into it this was intentionally added in And my comment has not been updated since dani-garcia/vaultwarden#6004 has been added. So it might be out of date. (I have not yet checked if there are further changes required.) |
|
Have you looked at the commit I've linked? That change was added in |
|
I am not saying that this is your fault. You clearly misunderstood my question: I don't have a bitwarden account, thus I do not know what the Send dialog looks like now. I also said that I haven't tested 2025.6.2 yet. I thought the missing options were the result of a bug in the bitwarden web client, since these options are available on the desktop client. As to your question, if I saw the commit you linked. Yes, I did. However, the bw commit messages and info in PRs are often useless, because they don't explain anything. The commit you sent mentioned that the send dialog was replaced. Well, great, but they didn't say that they removed 3 options and why. That's anyone's guess really. I'll create a bw account and open an issue at bw. |
Why do you think I misunderstood your question? Which question are you referring to? Your initial question or the one where you were being intentionally obtuse?
And I answered that this was probably done intentionally, so there's no confusion on my part about your question. I'm not sure what you were hoping by questioning the semantics of my answer. I've referenced the commit where this was changed and heavily implied that this was not fixed because it does not look like a bug to me.
Like I said, this is not the case. btw: the screenshot was from the |
bd68714 to
612c54c
Compare


The new web-vault
web-v2025.6.1has done away with a feature flag that requires some changes in the Vaultwarden backend that we have not implemented yet. I.e. deleting entries would not be possible with newer clients ( dani-garcia/vaultwarden#5996). So I would wait for a new Vaultwarden release before updating to the newest web-vault.