Skip to content

Releases: dani-garcia/vaultwarden

1.30.1

19 Nov 22:53
4883650
Compare
Choose a tag to compare

This is a minor release to fix some issues with the Login with device feature, and restore the alpine docker tag that was missing on the latest release.

⚠️ Note: The WebSockets service for live sync has been integrated in the main HTTP server, which means simpler proxy setups that don't require a separate rule to redirect WS traffic to port 3012. Please check the updated examples in the wiki. It's recommended to migrate to this new setup as using the old server on port 3012 is deprecated, won't receive new features and will be removed in a future release.

What's Changed

Full Changelog: 1.30.0...1.30.1

1.30.0

05 Nov 23:08
cec1e87
Compare
Choose a tag to compare

⚠️ Note: The WebSockets service for live sync has been integrated in the main HTTP server, which means simpler proxy setups that don't require a separate rule to redirect WS traffic to port 3012. Please check the updated examples in the wiki. It's recommended to migrate to this new setup as using the old server on port 3012 is deprecated, won't receive new features and will be removed in a future release.

Major changes and New Features

  • Added passkey support, allowing the browser extensions to store and use your passkeys, make sure the extension is updated to version 2023.10.0 or newer for passkey support.
  • Updated web vault to 2023.10.0.
  • Fixed crashes in ARMv6 devices
  • Fixed crashes when trying to create/edit a cipher in the mobile applications.

What's Changed

New Contributors

Full Changelog: 1.29.2...1.30.0

1.29.2

31 Aug 20:57
66bff73
Compare
Choose a tag to compare

Minor release to fix an issue forcing user to set amaster password when logging in even when it's already set

What's Changed

Full Changelog: 1.29.1...1.29.2

1.29.1

26 Jul 21:35
3dbfc48
Compare
Choose a tag to compare

Minor release to fix some issues with organization API key generation when using PostgreSQL

What's Changed

Full Changelog: 1.29.0...1.29.1

1.29.0

09 Jul 14:04
1c7338c
Compare
Choose a tag to compare

Major changes and New Features

  • WebSocket notifications now work via the default HTTP port. No need for WEBSOCKET_ENABLED and a separate port anymore.
    The proxy examples still need to be updated for this. Support for the old websockets port 3012 will remain for the time being.
  • Mobile Client push notification support, see #3304 thanks @GeekCornerGH!
  • Web-Vault updated to v2023.5.0 (v2023.5.1 does not add any improvements for us)
  • The latest Bitwarden Directory Connector can be used now (v2022.11.0)
  • Storing passkeys is supported, though the clients are not yet released. So, it might be we need to make some changes once they are released.
    See: #3593, thanks @GeekCornerGH!

What's Changed

New Contributors

Full Changelog: 1.28.1...1.29.0

1.28.1

02 Apr 21:36
0b28ab3
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: 1.28.0...1.28.1

1.28.0

26 Mar 18:11
3646f14
Compare
Choose a tag to compare

Major changes

  • The project has changed license to the AGPLv3. If you're hosting a Vaultwarden instance, you now have a requirement to distribute the Vaultwarden source code to your users if they request it. The source code, and any changes you have made, need to be under the same AGPLv3 license. If you simply use our code without modifications, just pointing them to this repository is enough.
  • Added support for Argon2 key derivation on the clients. To enable it for your account, make sure all your clients are using version v2023.2.0 or greater, then go to account settings > security > keys, and change the algorithm from PBKDF2 to Argon2id.
  • Added support for Argon2 key derivation for the admin page token. To update your admin token to use it, check the wiki
  • New alternative registries for the docker images are available (In BETA for now):

What's Changed

New Contributors

Full Changelog: 1.27.0...1.28.0

1.27.0

24 Dec 15:52
10dadfc
Compare
Choose a tag to compare

New features

Event logs for organizations

With this feature enabled, actions occurring inside an organization will be recorded in a log, viewable by organization admins and owners. Check the official documentation to learn more: https://bitwarden.com/help/event-logs/ (Note that the Public API is not yet implemented, so the events are only viewable in the Web Vault)

To enable this feature, set ORG_EVENTS_ENABLED=true. By default all events will be stored indefinitely, if you want to limit that, you can use the EVENTS_DAYS_RETAIN option. You can also tune the cleanup schedule with EVENT_CLEANUP_SCHEDULE.

Group support (beta)

Enables the creation and use of groups inside an organization. At the moment this is in beta because there are some known issues (#2989). Still, the more this feature is tested, the faster we will be able to stabilize it.

To enable this feature, set ORG_GROUPS_ENABLED=true, make sure to make proper backups of your instance before hand.

What's Changed

New Contributors

Full Changelog: 1.26.0...1.27.0

1.26.0

14 Oct 18:10
638766b
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: 1.25.2...1.26.0

1.25.2

27 Jul 18:43
ce9d930
Compare
Choose a tag to compare

⚠️ Reminder: If you are still using the bitwardenrs/server* Docker images, you need to migrate to the new vaultwarden image. Check #1642 for an explanation. The old images will not receive any new updates any longer.

Important

An incompatibility between the format in which some Bitwarden clients upload attachments and sends could lead to those uploads being silently corrupted. We believe this is occurring only when using the mobile clients and only on the latest vaultwarden 1.25.1.
To mitigate this issue, we're releasing this quick patch to make any upload that could lead to a corrupted file explicitly return an error, notifying the user of the problem.
We recommend updating as soon as possible, and checking that any recently uploaded attachments can be downloaded and opened correctly (The corrupted uploads will return an error when downloading or download a very small file).

We've also fixed the docker volume check added in 1.25.1, if you previously needed to set I_REALLY_WANT_VOLATILE_STORAGE=true to start the container, please try again without it, and open an issue if it still won't start.

What's Changed

Full Changelog: 1.25.1...1.25.2