mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-26 09:46:00 +03:00
[GH-ISSUE #3351] Vaultwarden Admin inconsistently displaying web version #1538
Labels
No labels
SSO
Third party
better for forum
bug
bug
documentation
duplicate
enhancement
future Vault
future Vault
future Vault
good first issue
help wanted
low priority
notes
pull-request
question
troubleshooting
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/vaultwarden#1538
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Originally created by @pc-coholic on GitHub (Mar 17, 2023).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/3351
Vaultwarden Admin inconsistently displaying web version
When looking at the diagnostics-section of the Vaultwarden Admin page, the installed webvault-version is displayed with a
v-prefix, which is absent from the latest webvault version. It seems like as a result, the yellowUpdate-flag is also incorrectly applied.Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden:
Steps to reproduce
Expected behaviour
Either the
Web installedversion string should lose or theWeb Latestneeds to get thev, so that the greenOKor yellowUpdate-label are correctly displayed.Actual behaviour
Web Latestversion is displayed with av-prefix asv2023.2.20Web Installedversion is displayed without av-prefix as2023.2.20Update-label is displayedTroubleshooting data
I auto-update the server component by using
docker-image-extractand update the webvault by frabbing the latest release from https://api.github.com/repos/dani-garcia/bw_web_builds/releases/latestI don't see why, but I'm mentioning it, in case this could be the root cause of this issue.
On a separate note: The support-string even outputs the installed version with
vv...@BlackDex commented on GitHub (Mar 17, 2023):
This is already fixed in testing
@pc-coholic commented on GitHub (Mar 17, 2023):
Must have somehow got past me when I looked through the commits. My apologies.
@BlackDex commented on GitHub (Mar 17, 2023):
It was part of this PR: #3281