Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(container): update image vaultwarden/server to v1.30.5 #31

Merged
merged 1 commit into from
Mar 18, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 3, 2024

Mend Renovate

This PR contains the following updates:

Package Type Update Change
vaultwarden/server stage patch 1.30.1-alpine -> 1.30.5-alpine

Release Notes

dani-garcia/vaultwarden (vaultwarden/server)

v1.30.5

Compare Source

What's Changed

New Contributors

Full Changelog: dani-garcia/vaultwarden@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: dani-garcia/vaultwarden@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: dani-garcia/vaultwarden@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: dani-garcia/vaultwarden@1.30.1...1.30.2


Configuration

📅 Schedule: Branch creation - "on saturday" (UTC), 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.


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

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot changed the title fix(container): update image vaultwarden/server to v1.30.3 fix(container): update image vaultwarden/server to v1.30.4 Mar 2, 2024
@renovate renovate bot force-pushed the renovate/vaultwarden-server-1.x branch from 931749d to e5fa017 Compare March 2, 2024 16:50
@renovate renovate bot changed the title fix(container): update image vaultwarden/server to v1.30.4 fix(container): update image vaultwarden/server to v1.30.5 Mar 2, 2024
@renovate renovate bot force-pushed the renovate/vaultwarden-server-1.x branch from e5fa017 to ced829b Compare March 2, 2024 22:28
@arthurgeek arthurgeek merged commit 443df1f into main Mar 18, 2024
@arthurgeek arthurgeek deleted the renovate/vaultwarden-server-1.x branch March 18, 2024 15:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant