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
Deploy bw-unified, latest version, no matter which db.
Open admin portal.
Expected Result
If server/web version installed is higher than server/web version latest no call sign should be next to version installed.
Actual Result
If server/web version installed is higher than server/web version latest, a call sign on the admin portal says: "This version is not the latest. You should update."
I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
The text was updated successfully, but these errors were encountered:
Hi there,
Thank you for your report! I have flagged this to our engineering team.
If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time - our engineering team will be happy to review these.
Due to the build release process of unified while it is in beta, this is expected. The versions displaying in the admin portal are that of the current latest for the standard deployment. I expect these version to continue to be a little off until we release unified GA and release it during the same process as the standard deployment. I will leave this issue open for others to find but we aren't going to be fixing this until GA.
Steps To Reproduce
Deploy bw-unified, latest version, no matter which db.
Open admin portal.
Expected Result
If server/web version installed is higher than server/web version latest no call sign should be next to version installed.
Actual Result
If server/web version installed is higher than server/web version latest, a call sign on the admin portal says: "This version is not the latest. You should update."
Screenshots or Videos
Additional Context
No response
Githash Version
ff491ec-dirty
Environment Details
No response
Database Image
No response
Issue-Link
#2480
Issue Tracking Info
The text was updated successfully, but these errors were encountered: