fix(container): update image vaultwarden/server to v1.30.5 #81
Loading…
Reference in New Issue
No description provided.
Delete Branch "renovate/vaultwarden-server-1.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
1.30.1
->1.30.5
Release Notes
dani-garcia/vaultwarden (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
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 PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.
fix(container): update image vaultwarden/server to v1.30.2to fix(container): update image vaultwarden/server to v1.30.34db6a9f893
to6d69e9d430
6d69e9d430
toeccf67f236
fix(container): update image vaultwarden/server to v1.30.3to fix(container): update image vaultwarden/server to v1.30.4eccf67f236
toadd1ae7775
fix(container): update image vaultwarden/server to v1.30.4to fix(container): update image vaultwarden/server to v1.30.5