[GH-ISSUE #774] web-vault patch doesn't work with v2.12.0 #533

New issue

Closed

opened 2026-03-03 01:30:16 +03:00 by kerem · 2 comments

kerem commented

2026-03-03 01:30:16 +03:00

Owner

Originally created by @pdarcos on GitHub (Dec 20, 2019).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/774

As the title says, I'm following the wiki and there's no v2.12.0 patch available, so I tried using the available v2.11.0.patch but git doesn't like it.

:~/web-vault# git apply v2.11.0.patch
error: unrecognized input

Does the patch need updating to be compatible with current v.2.12.0?

Originally created by @pdarcos on GitHub (Dec 20, 2019). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/774 As the title says, I'm following the wiki and there's no v2.12.0 patch available, so I tried using the available v2.11.0.patch but git doesn't like it. :~/web-vault# git apply v2.11.0.patch error: unrecognized input Does the patch need updating to be compatible with current v.2.12.0?

kerem closed this issue

2026-03-03 01:30:17 +03:00

kerem commented

2026-03-03 01:30:18 +03:00

Author

Owner

@manofthepeace commented on GitHub (Dec 20, 2019):

It works fine with latest web vault code;

cd code/bitwarden/web (This is the official "web" repo of bitwarden)
git apply ../bw_web_builds/patches/v2.11.0.patch (dani-garcia's repo)

Otherwise you can just use the prebuilt vault from here; https://github.com/dani-garcia/bw_web_builds/releases then you dont need to patch and build yourself.

@manofthepeace commented on GitHub (Dec 20, 2019): It works fine with latest web vault code; cd code/bitwarden/web (This is the official "web" repo of bitwarden) git apply ../bw_web_builds/patches/v2.11.0.patch (dani-garcia's repo) Otherwise you can just use the prebuilt vault from here; https://github.com/dani-garcia/bw_web_builds/releases then you dont need to patch and build yourself.

kerem commented

2026-03-03 01:30:18 +03:00

Author

Owner

@pdarcos commented on GitHub (Dec 21, 2019):

Sorry. Silly mistake.
Working fine indeed

@pdarcos commented on GitHub (Dec 21, 2019): Sorry. Silly mistake. Working fine indeed