Unified Beta Self-Host v2024.1.2 includes web 2024.1.1 when release notes indicate web 2024.1.2

[holow29]

Steps To Reproduce

Deploy latest beta tag/v2024.1.2

Expected Result

Web v2024.1.2 included

Actual Result

Web v2024.1.1 included

Screenshots or Videos

No response

Additional Context

Release notes for 2024.1.2 show web updated to 2024.1.2, but the admin panel for the latest Unified Beta 2024.1.2 shows "Web Installed 2024.1.1" and the footer of the web client included with that release indicates the same.

I bring this up mainly because it might indicate a bug in the build and deployment pipeline for the unified docker containers/tags.

Githash Version

dca8d00-dirty

Environment Details

No response

Database Image

No response

Issue-Link

#2480

Issue Tracking Info

• 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.

[cbbit]

Hi there,

Thank you for your report!

I was able to reproduce this issue, and 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.

Thanks once again!

[holow29]

Likewise, v2024.2.2 unified self-host beta includes web 2024.2.2 whereas release notes indicate 2024.2.5. WIthout looking at the actions responsible for triggering the docker container build, it appears to be tied to bitwarden/server and not bitwarden/self-host, which means that it will often not have the latest web version - conflicting with the release notes and the non-unified self-host.