-
-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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
vaultwarden: 1.31.0 -> 1.32.0 #334048
vaultwarden: 1.31.0 -> 1.32.0 #334048
Conversation
https://github.com/dani-garcia/vaultwarden/releases/tag/1.32.0 "This release has several CVE Reports fixed and we recommend everybody to update to the latest version as soon as possible." So a backport to 24.05 is in order. |
We need to create the backports PR manually. Will do that soon ™️ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
did a quick smoke test and nothing immediately exploded
This pull request has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/several-information-leaks-in-vaultwarden-1-32-0/50500/1 |
Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for vaultwarden is: Unofficial Bitwarden compatible server written in Rust
meta.homepage for vaultwarden is: https://github.com/dani-garcia/vaultwarden
meta.changelog for vaultwarden is: https://github.com/dani-garcia/vaultwarden/releases/tag/1.32.0
closes #334047
closes #334046
Updates performed
To inspect upstream changes
Release on GitHub
Compare changes on GitHub
Impact
Checks done
passthru.tests
, if any, passedRebuild report (if merged into master) (click to expand)
Instructions to test this update (click to expand)
Either download from Cachix:
(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the
trusted-users
list or you can usesudo
since root is effectively trusted.Or, build yourself:
Or:
After you've downloaded or built it, look at the files and if there are any, run the binaries:
Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of
nixpkgs-review
run on x86_64-linux 11 package blacklisted:
3 packages built:
Maintainer pings
cc @dotlambda @SuperSandro2000 for testing.
Add a 👍 reaction to pull requests you find important.