Skip to content
This repository has been archived by the owner on Mar 24, 2024. It is now read-only.

chore(deps): update container image docker.io/vaultwarden/server to v1.30.5 #531

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(deps): update container image docker.io/vaultwarden/server to v1.30.5 #531

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 9, 2023 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Update Change
docker.io/vaultwarden/server minor 1.26.0 -> 1.30.5

Warning

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

Release Notes

dani-garcia/vaultwarden (docker.io/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

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

New Contributors

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

v1.27.0

Compare Source

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

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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/docker.io-vaultwarden-server-1.x branch from 301ae2b to a3d1251 Compare March 26, 2023 21:51
@renovate renovate bot changed the title chore(deps): update container image docker.io/vaultwarden/server to v1.27.0 chore(deps): update container image docker.io/vaultwarden/server to v1.28.0 Mar 26, 2023
@renovate renovate bot force-pushed the renovate/docker.io-vaultwarden-server-1.x branch from a3d1251 to dba4c03 Compare April 3, 2023 00:20
@renovate renovate bot changed the title chore(deps): update container image docker.io/vaultwarden/server to v1.28.0 chore(deps): update container image docker.io/vaultwarden/server to v1.28.1 Apr 3, 2023
@renovate renovate bot changed the title chore(deps): update container image docker.io/vaultwarden/server to v1.28.1 chore(deps): update container image docker.io/vaultwarden/server to v1.29.0 Jul 9, 2023
@renovate renovate bot force-pushed the renovate/docker.io-vaultwarden-server-1.x branch from dba4c03 to fe3486b Compare July 9, 2023 16:54
@renovate renovate bot changed the title chore(deps): update container image docker.io/vaultwarden/server to v1.29.0 chore(deps): update container image docker.io/vaultwarden/server to v1.29.1 Jul 27, 2023
@renovate renovate bot force-pushed the renovate/docker.io-vaultwarden-server-1.x branch from fe3486b to cedcc49 Compare July 27, 2023 01:23
@renovate renovate bot force-pushed the renovate/docker.io-vaultwarden-server-1.x branch from cedcc49 to 1f1fff6 Compare September 1, 2023 02:20
@renovate renovate bot changed the title chore(deps): update container image docker.io/vaultwarden/server to v1.29.1 chore(deps): update container image docker.io/vaultwarden/server to v1.29.2 Sep 1, 2023
@renovate renovate bot force-pushed the renovate/docker.io-vaultwarden-server-1.x branch from 1f1fff6 to a906c9a Compare November 6, 2023 01:17
@renovate renovate bot changed the title chore(deps): update container image docker.io/vaultwarden/server to v1.29.2 chore(deps): update container image docker.io/vaultwarden/server to v1.30.0 Nov 6, 2023
@renovate renovate bot changed the title chore(deps): update container image docker.io/vaultwarden/server to v1.30.0 chore(deps): update container image docker.io/vaultwarden/server to v1.30.1 Nov 20, 2023
@renovate renovate bot force-pushed the renovate/docker.io-vaultwarden-server-1.x branch from a906c9a to 5a47efe Compare November 20, 2023 02:16
@renovate renovate bot force-pushed the renovate/docker.io-vaultwarden-server-1.x branch from 5a47efe to 4487e81 Compare January 30, 2024 22:23
@renovate renovate bot changed the title chore(deps): update container image docker.io/vaultwarden/server to v1.30.1 chore(deps): update container image docker.io/vaultwarden/server to v1.30.2 Jan 30, 2024
@renovate renovate bot force-pushed the renovate/docker.io-vaultwarden-server-1.x branch from 4487e81 to 5ab0f7b Compare February 1, 2024 23:17
@renovate renovate bot changed the title chore(deps): update container image docker.io/vaultwarden/server to v1.30.2 chore(deps): update container image docker.io/vaultwarden/server to v1.30.3 Feb 1, 2024
@renovate renovate bot force-pushed the renovate/docker.io-vaultwarden-server-1.x branch from 5ab0f7b to 82f550b Compare March 2, 2024 14:54
@renovate renovate bot changed the title chore(deps): update container image docker.io/vaultwarden/server to v1.30.3 chore(deps): update container image docker.io/vaultwarden/server to v1.30.4 Mar 2, 2024
@renovate
chore(deps): update container image docker.io/vaultwarden/server to v…
da26499 
…1.30.5

Signed-off-by: Patrik Cyvoct <Sh4d1@users.noreply.github.com>
@renovate renovate bot force-pushed the renovate/docker.io-vaultwarden-server-1.x branch from 82f550b to da26499 Compare March 2, 2024 19:42
@renovate renovate bot changed the title chore(deps): update container image docker.io/vaultwarden/server to v1.30.4 chore(deps): update container image docker.io/vaultwarden/server to v1.30.5 Mar 2, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers
No reviews
Assignees
No one assigned
Labels
dep/minor renovate/image
Projects
None yet
Milestone
No milestone
Development

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