container
/
vaultwarden
1
0
Fork 0
Code Issues 1 Pull Requests Releases 54 Activity

chore(deps): update bitwarden packages - autoclosed #38

Closed
renovator wants to merge 1 commits from renovate/bitwarden-packages into main
pull from: renovate/bitwarden-packages
merge into: container:main
Conversation 0 Commits 1 Files Changed 2 +2 -2
renovator commented 2021-04-30 02:00:42 +02:00
Member
Copy Link

This PR contains the following updates:

Package Update Change
dani-garcia/bitwarden_rs minor 1.20.0 -> 1.21.0
dani-garcia/bw_web_builds minor v2.19.0 -> v2.20.1

Release Notes

dani-garcia/bitwarden_rs

v1.21.0

Compare Source

Update 20201-04-30: This release has been pushed again to fix an issue with the Docker builds building an older revision of the project.

Project renamed to vaultwarden

Due to user confusion and to avoid any possible trademark/brand issues with the official server, this project is going to be renamed to vaultwarden. This rename might mean you will need to make some changes to your setup.

Docker users

  • If you are using any of the docker images, you will have to migrate to the new image under the vaultwarden organization:
vaultwarden/server

The new image is equivalent to the old one except for the name, so the upgrade is as simple as removing the old container and creating a new one with the new image, making sure the rest of parameters are the same. For example, if you used the default docker run command mentioned in the readme, and upgrade would be done like this:

### Stop and remove the old container
docker stop bitwarden
docker rm bitwarden
### Start new container with the data mounted, make sure the path is the same as the previous one
docker run -d --name vaultwarden -v /bw-data/:/data/ -p 80:80 vaultwarden/server:latest

Note that the old images aren't gone yet, just deprecated. They will keep being updated for another two releases after this one to avoid breakage, but it's recommended to migrate to the new image as soon as possible.

If you are still using the old database specific images (server-mysql and server-postgresql), they are also deprecated since the main server image supports all three databases at the same time, more info on release 1.17.0.

If you are using the startup scripts mounted inside the container (/etc/bitwarden_rs.sh and /etc/bitwarden_rs.d/*), they will now load with the vaultwarden name first and the bitwarden_rs name as a fallback for compatibility, but it's recommended to rename them as well.

Git users

If you are using the git repository, we've used this opportunity to rename the master branch to main, so make sure to have that in mind. The rest of the process is the same and GitHub will redirect the old remote URL to the new one, simply note that the binary generated by cargo is now named vaultwarden instead of bitwarden_rs.

Changelog

  • Add support for enabling auto-deletion of trash items after X days, disabled by default
    • Set TRASH_AUTO_DELETE_DAYS to a positive value to enable this functionality
    • You can also configure how often this process runs, using cron sintax with the variable TRASH_PURGE_SCHEDULE
  • Updates to the icon fetching, making it more reliable in detecting icon types
  • Updated admin page, improving version checks and SQLite backup feature
dani-garcia/bw_web_builds

v2.20.1

Compare Source

https://github.com/bitwarden/web/releases/tag/v2.20.1

Configuration

📅 Schedule: 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

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

This PR has been generated by Renovate Bot.

This PR contains the following updates: | Package | Update | Change | |---|---|---| | [dani-garcia/bitwarden_rs](https://github.com/dani-garcia/bitwarden_rs) | minor | `1.20.0` -> `1.21.0` | | [dani-garcia/bw_web_builds](https://github.com/dani-garcia/bw_web_builds) | minor | `v2.19.0` -> `v2.20.1` | --- ### Release Notes <details> <summary>dani-garcia/bitwarden_rs</summary> ### [`v1.21.0`](https://github.com/dani-garcia/bitwarden_rs/releases/1.21.0) [Compare Source](https://github.com/dani-garcia/bitwarden_rs/compare/1.20.0...1.21.0) Update 20201-04-30: This release has been pushed again to fix an issue with the Docker builds building an older revision of the project. ### Project renamed to vaultwarden Due to user confusion and to avoid any possible trademark/brand issues with the official server, this project is going to be renamed to vaultwarden. This rename might mean you will need to make some changes to your setup. #### Docker users - If you are using any of the docker images, you will have to migrate to the new image under the vaultwarden organization: ##### `vaultwarden/server` The new image is equivalent to the old one except for the name, so the upgrade is as simple as removing the old container and creating a new one with the new image, making sure the rest of parameters are the same. For example, if you used the default `docker run` command mentioned in the readme, and upgrade would be done like this: ```sh ### Stop and remove the old container docker stop bitwarden docker rm bitwarden ### Start new container with the data mounted, make sure the path is the same as the previous one docker run -d --name vaultwarden -v /bw-data/:/data/ -p 80:80 vaultwarden/server:latest ``` Note that the old images aren't gone yet, just deprecated. They will keep being updated for another two releases after this one to avoid breakage, but it's recommended to migrate to the new image as soon as possible. If you are still using the old database specific images (server-mysql and server-postgresql), they are also deprecated since the main server image supports all three databases at the same time, [more info on release 1.17.0](https://github.com/dani-garcia/vaultwarden/releases/tag/1.17.0). If you are using the startup scripts mounted inside the container (`/etc/bitwarden_rs.sh` and `/etc/bitwarden_rs.d/*`), they will now load with the vaultwarden name first and the bitwarden_rs name as a fallback for compatibility, but it's recommended to rename them as well. #### Git users If you are using the git repository, we've used this opportunity to rename the `master` branch to `main`, so make sure to have that in mind. The rest of the process is the same and GitHub will redirect the old remote URL to the new one, simply note that the binary generated by cargo is now named `vaultwarden` instead of `bitwarden_rs`. ### Changelog - Add support for enabling auto-deletion of trash items after X days, disabled by default - Set `TRASH_AUTO_DELETE_DAYS` to a positive value to enable this functionality - You can also configure how often this process runs, using cron sintax with the variable `TRASH_PURGE_SCHEDULE` - Updates to the icon fetching, making it more reliable in detecting icon types - Updated admin page, improving version checks and SQLite backup feature </details> <details> <summary>dani-garcia/bw_web_builds</summary> ### [`v2.20.1`](https://github.com/dani-garcia/bw_web_builds/releases/v2.20.1) [Compare Source](https://github.com/dani-garcia/bw_web_builds/compare/v2.19.0...v2.20.1) <https://github.com/bitwarden/web/releases/tag/v2.20.1> </details> --- ### Configuration 📅 **Schedule**: 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. 👻 **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://github.com/renovatebot/renovate/discussions) if that's undesired. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box. --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).
renovator changed title from chore(deps): update dependency dani-garcia/bitwarden_rs to v1.21.0 to chore(deps): update bitwarden packages 2021-05-13 23:01:25 +02:00
renovator force-pushed renovate/bitwarden-packages from 8aea00c0c1 to dc44c0cc34 2021-05-13 23:01:26 +02:00 Compare
renovator changed title from chore(deps): update bitwarden packages to chore(deps): update bitwarden packages - autoclosed 2021-05-15 15:01:27 +02:00
renovator closed this pull request 2021-05-15 15:01:27 +02:00
Some checks failed
continuous-integration/drone/pr Build is failing
Details

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: container/vaultwarden#38
No description provided.
Delete Branch "renovate/bitwarden-packages"

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?