Skip to content

chore(deps): update quay.io/vaultwarden/server docker tag to v1.30.5

Lama Bot requested to merge renovate/quay.io-vaultwarden-server-1.x into main

This MR contains the following updates:

Package Update Change
quay.io/vaultwarden/server minor 1.29.2 -> 1.30.5

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

dani-garcia/vaultwarden (quay.io/vaultwarden/server)

v1.30.5

Compare Source

What's Changed

New Contributors

Full Changelog: https://github.com/dani-garcia/vaultwarden/compare/1.30.4...1.30.5

v1.30.4

Compare Source

️ 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 the next release.

What's Changed

New Contributors

Full Changelog: https://github.com/dani-garcia/vaultwarden/compare/1.30.3...1.30.4

v1.30.3

Compare Source

This is a minor release to fix some issues with push notification device registration and docker healthcheck.

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 the next release.

What's Changed

Full Changelog: https://github.com/dani-garcia/vaultwarden/compare/1.30.2...1.30.3

v1.30.2

Compare Source

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 the next release.

What's Changed

New Contributors

Full Changelog: https://github.com/dani-garcia/vaultwarden/compare/1.30.1...1.30.2

v1.30.1

Compare Source

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: https://github.com/dani-garcia/vaultwarden/compare/1.30.0...1.30.1

v1.30.0

Compare Source

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: https://github.com/dani-garcia/vaultwarden/compare/1.29.2...1.30.0


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever MR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this MR and you won't be reminded about this update again.


  • If you want to rebase/retry this MR, check this box

This MR has been generated by Renovate Bot.

Edited by Lama Bot

Merge request reports