[GH-ISSUE #441] [Question] LTS & how are Bitwarden updates handled? #262

New issue

Closed

opened 2026-03-03 01:27:23 +03:00 by kerem · 2 comments

kerem commented

2026-03-03 01:27:23 +03:00

Owner

Originally created by @advename on GitHub (Mar 25, 2019).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/441

I'm thinking about implementing this rust version for our company because all our servers use ZFS as system partition (not supported by official Bitwarden) and changing to Ext4 is currently not an option.

I'm wondering how the is the LTS looking for this project? And how are bitwarden updates handled? Do they need to be manually implemented into this project or are updates non dependant from Bitwarden_rs?

Originally created by @advename on GitHub (Mar 25, 2019). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/441 I'm thinking about implementing this rust version for our company because all our servers use ZFS as system partition (not supported by official Bitwarden) and changing to Ext4 is currently not an option. I'm wondering how the is the LTS looking for this project? And how are bitwarden updates handled? Do they need to be manually implemented into this project or are updates non dependant from Bitwarden_rs?

kerem

2026-03-03 01:27:23 +03:00

closed this issue
added the
question
label

kerem commented

2026-03-03 01:27:23 +03:00

Author

Owner

@dani-garcia commented on GitHub (Mar 25, 2019):

We don't offer any long term support guaranteees because I don't have the bandwidth to maintain multiple versions, but I try to keep compatibility in mind and make sure that the upgrade path from one version to the next is as simple as possible, so it should be easy to keep up to date using the latest release.

We don't have automatic server updates or any kind of update notifications, but you can subscribe to the GitHub releases to be kept up-to-date.

As far as the client updates, most of them don't have breaking changes, so they should work without any modifications. If they add any new functionality or they change some API calls, then there is a chance that it would require a server update to work. This doesn't happen very often, and I try to keep up with the upstream changes to make sure that the project isn't left too far behind, but it's not perfect.

@dani-garcia commented on GitHub (Mar 25, 2019): We don't offer any long term support guaranteees because I don't have the bandwidth to maintain multiple versions, but I try to keep compatibility in mind and make sure that the upgrade path from one version to the next is as simple as possible, so it should be easy to keep up to date using the latest release. We don't have automatic server updates or any kind of update notifications, but you can subscribe to the GitHub releases to be kept up-to-date. As far as the client updates, most of them don't have breaking changes, so they should work without any modifications. If they add any new functionality or they change some API calls, then there is a chance that it would require a server update to work. This doesn't happen very often, and I try to keep up with the upstream changes to make sure that the project isn't left too far behind, but it's not perfect.

kerem commented

2026-03-03 01:27:24 +03:00

Author

Owner

@mprasil commented on GitHub (Apr 10, 2019):

I think this was answered and can be closed now. Feel free to reopen if you have further questions regarding this.

@mprasil commented on GitHub (Apr 10, 2019): I think this was answered and can be closed now. Feel free to reopen if you have further questions regarding this.