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.

Sign up for GitHub

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

Jump to bottom

Update docker.io/vaultwarden/server Docker tag to v1.32.0 - autoclosed #43

Closed
wants to merge 1 commit into from
Closed

Update docker.io/vaultwarden/server Docker tag to v1.32.0 - autoclosed #43

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 26, 2023 •
edited
Loading

This PR contains the following updates:

Package Update Change
docker.io/vaultwarden/server minor 1.27.0 -> 1.32.0

Release Notes

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

v1.32.0

Compare Source

Security Fixes

This release has several CVE Reports fixed and we recommend everybody to update to the latest version as soon as possible.

Other changes

  • Updated web-vault to v2024.6.2
  • Fixed issues with password reset enrollment by rolling back a web-vault commit

What's Changed

New Contributors

Full Changelog: dani-garcia/vaultwarden@1.31.0...1.32.0

v1.31.0

Compare Source

Major changes and New Features

  • Initial support for the beta releases of the new native mobile apps
  • Removed support for WebSocket traffic on port 3012, as it's been integrated on the main HTTP port for a few releases
  • Updated included web vault to 2024.5.1

General mention

Bitwarden has changed the push API endpoints which affects the EU region endpoint users.
So if you use the push functionality and use the EU region you need to make some changes.
You have to update push.bitwarden.eu to api.bitwarden.eu.
This is also an issue with any previous version of Vaultwarden.

What's Changed

New Contributors

Full Changelog: dani-garcia/vaultwarden@1.30.5...1.31.0

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

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: dani-garcia/vaultwarden@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: dani-garcia/vaultwarden@1.29.2...1.30.0

v1.29.2

Compare Source

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: dani-garcia/vaultwarden@1.29.1...1.29.2

v1.29.1

Compare Source

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

What's Changed

Full Changelog: dani-garcia/vaultwarden@1.29.0...1.29.1

v1.29.0

Compare Source

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: dani-garcia/vaultwarden@1.28.1...1.29.0

v1.28.1

Compare Source

What's Changed

New Contributors

Full Changelog: dani-garcia/vaultwarden@1.28.0...1.28.1

v1.28.0

Compare Source

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

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.

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

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/docker.io-vaultwarden-server-1.x branch from 4eebb5e to a660af8 Compare April 3, 2023 01:40
@renovate renovate bot changed the title chore(deps): update docker.io/vaultwarden/server docker tag to v1.28.0 chore(deps): update docker.io/vaultwarden/server docker tag to v1.28.1 Apr 3, 2023
@renovate renovate bot changed the title chore(deps): update docker.io/vaultwarden/server docker tag to v1.28.1 chore(deps): update docker.io/vaultwarden/server docker tag to v1.29.0 Jul 9, 2023
@renovate renovate bot force-pushed the renovate/docker.io-vaultwarden-server-1.x branch from a660af8 to 060c9cc Compare July 9, 2023 15:50
@renovate renovate bot changed the title chore(deps): update docker.io/vaultwarden/server docker tag to v1.29.0 chore(deps): update docker.io/vaultwarden/server docker tag to v1.29.1 Jul 27, 2023
@renovate renovate bot force-pushed the renovate/docker.io-vaultwarden-server-1.x branch from 060c9cc to 1e194d4 Compare July 27, 2023 00:38
@renovate renovate bot changed the title chore(deps): update docker.io/vaultwarden/server docker tag to v1.29.1 Update docker.io/vaultwarden/server Docker tag to v1.29.1 Aug 12, 2023
@renovate renovate bot force-pushed the renovate/docker.io-vaultwarden-server-1.x branch from 1e194d4 to 739be10 Compare August 20, 2023 15:30
@renovate renovate bot changed the title Update docker.io/vaultwarden/server Docker tag to v1.29.1 Update docker.io/vaultwarden/server Docker tag to v1.29.2 Sep 1, 2023
@renovate renovate bot force-pushed the renovate/docker.io-vaultwarden-server-1.x branch from 739be10 to 80b4518 Compare September 1, 2023 01:41
@renovate renovate bot changed the title Update docker.io/vaultwarden/server Docker tag to v1.29.2 Update docker.io/vaultwarden/server Docker tag to v1.30.0 Nov 6, 2023
@renovate renovate bot force-pushed the renovate/docker.io-vaultwarden-server-1.x branch from 80b4518 to 8a8a1bd Compare November 6, 2023 01:01
@renovate renovate bot changed the title Update docker.io/vaultwarden/server Docker tag to v1.30.0 Update docker.io/vaultwarden/server Docker tag to v1.30.1 Nov 20, 2023
@renovate renovate bot force-pushed the renovate/docker.io-vaultwarden-server-1.x branch from 8a8a1bd to 042cb65 Compare November 20, 2023 02:21
@renovate renovate bot changed the title Update docker.io/vaultwarden/server Docker tag to v1.30.1 chore(deps): update docker.io/vaultwarden/server docker tag to v1.30.1 Dec 19, 2023
@renovate renovate bot force-pushed the renovate/docker.io-vaultwarden-server-1.x branch from 042cb65 to 2c0b147 Compare January 30, 2024 22:07
@renovate renovate bot changed the title chore(deps): update docker.io/vaultwarden/server docker tag to v1.30.1 chore(deps): update docker.io/vaultwarden/server docker tag to v1.30.2 Jan 30, 2024
@renovate renovate bot force-pushed the renovate/docker.io-vaultwarden-server-1.x branch from 2c0b147 to 800d940 Compare February 2, 2024 01:27
@renovate renovate bot changed the title chore(deps): update docker.io/vaultwarden/server docker tag to v1.30.2 chore(deps): update docker.io/vaultwarden/server docker tag to v1.30.3 Feb 2, 2024
@renovate renovate bot changed the title chore(deps): update docker.io/vaultwarden/server docker tag to v1.30.3 Update docker.io/vaultwarden/server Docker tag to v1.30.3 Feb 12, 2024
@renovate renovate bot force-pushed the renovate/docker.io-vaultwarden-server-1.x branch from 800d940 to c4ca4c3 Compare March 2, 2024 16:53
@renovate renovate bot changed the title Update docker.io/vaultwarden/server Docker tag to v1.30.3 Update docker.io/vaultwarden/server Docker tag to v1.30.4 Mar 2, 2024
@renovate renovate bot force-pushed the renovate/docker.io-vaultwarden-server-1.x branch from c4ca4c3 to 6c349e3 Compare March 2, 2024 22:11
@renovate renovate bot changed the title Update docker.io/vaultwarden/server Docker tag to v1.30.4 Update docker.io/vaultwarden/server Docker tag to v1.30.5 Mar 2, 2024
@renovate renovate bot force-pushed the renovate/docker.io-vaultwarden-server-1.x branch from 6c349e3 to 3e9512a Compare July 9, 2024 01:45
@renovate renovate bot changed the title Update docker.io/vaultwarden/server Docker tag to v1.30.5 Update docker.io/vaultwarden/server Docker tag to v1.31.0 Jul 9, 2024
@renovate renovate bot force-pushed the renovate/docker.io-vaultwarden-server-1.x branch from 3e9512a to 784b82e Compare August 11, 2024 19:00
@renovate renovate bot changed the title Update docker.io/vaultwarden/server Docker tag to v1.31.0 Update docker.io/vaultwarden/server Docker tag to v1.32.0 Aug 11, 2024
@renovate renovate bot changed the title Update docker.io/vaultwarden/server Docker tag to v1.32.0 Update docker.io/vaultwarden/server Docker tag to v1.32.0 - autoclosed Aug 29, 2024
@renovate renovate bot closed this Aug 29, 2024
@renovate renovate bot deleted the renovate/docker.io-vaultwarden-server-1.x branch August 29, 2024 23:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants