You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- DietPi-Software | vaultwarden: Our builds will now show the package version within the web UI. Many thanks to @gh3597 for reporting it missing and how to add it: #7364
Many thanks for reporting. This should add it. I am currently testing builds with the new native GitHub Actions ARM runners. Once this all works, and those builds do indeed show the version in the web UI, I can push the resulting packages to our APT server: 333bd4e
Required Information
DietPi v9.8.0
(although this issue has been apparent in multiple versions previous to this going back for a couple of years)bullseye
Linux vaultwarden 5.10.0-33-amd64 #1 SMP Debian 5.10.226-1 (2024-10-03) x86_64 GNU/Linux
Virtual Machine (x86_64)
Additional Information (if applicable)
vaultwarden
Steps to reproduce
Log in to the admin panel of vaultwarden.
![Image](https://private-user-images.githubusercontent.com/118667161/404695234-3ab76ea3-63b8-4237-a7b8-c4b872735690.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkyODc0OTQsIm5iZiI6MTczOTI4NzE5NCwicGF0aCI6Ii8xMTg2NjcxNjEvNDA0Njk1MjM0LTNhYjc2ZWEzLTYzYjgtNDIzNy1hN2I4LWM0Yjg3MjczNTY5MC5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUwMjExJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MDIxMVQxNTE5NTRaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT02MWI5N2FjNzMyYWI0OTQ2ZDIxZmY5Y2E0Yzg1NjAyYzliMDcwMTUwMmNhMWVjYWE3OWFmNGE1MWI0OGFlN2U4JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.nFLTeITauN5pPJn2Lwt_OczsR9WJv4lnLDfC4dAYRM8)
Go to diagnostics
View the blank space where current version should be
Expected behaviour
Vaultwarden version should be displayed.
Actual behaviour
Version is not being populated.
Extra details
I posted this as an issue with vaultwarden but they have passed it back to the packager.
Some info from that discussion. dani-garcia/vaultwarden#4936
The text was updated successfully, but these errors were encountered: