starred/vaultwarden
1
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2025-12-09 17:23:04 +03:00
Code Issues 429 Packages Projects Releases 10 Wiki Activity

bitwardenrs/server:latest showing as 1.14.2-1aa5e0d4 #1699

New Issue
Closed
opened 2025-10-09 17:26:04 +03:00 by OVERLORD · 3 comments
OVERLORD commented 2025-10-09 17:26:04 +03:00
Owner
Copy Link

Originally created by @giteke on GitHub.

Subject of the issue

After server:latest install, 1.14.2-1aa5e0d4 is shown as installed version on admin diagnostic page instead of 1.15.0-1aa5e0d4

Your environment

  • Bitwarden_rs version: 1.14.2-1aa5e0d4
  • Install method: Docker
  • Clients used:
  • Reverse proxy and version:
  • Version of mysql/postgresql:
  • Other relevant information:

Steps to reproduce

Expected behaviour

"Server installed" and "server latest" should be the same

Actual behaviour

Server Installed: 1.14.2-1aa5e0d4
Server Latest:

1.15.0-1aa5e0d4

Relevant logs

bwrs

Originally created by @giteke on GitHub. <!-- Please fill out the following template to make solving your problem easier and faster for us. This is only a guideline. If you think that parts are unneccessary for your issue, feel free to remove them. Remember to hide/obfuscate personal and confidential information, such as names, global IP/DNS adresses and especially passwords, if neccessary. --> ### Subject of the issue <!-- Describe your issue here.--> After server:latest install, 1.14.2-1aa5e0d4 is shown as installed version on admin diagnostic page instead of 1.15.0-1aa5e0d4 ### Your environment <!-- The version number, obtained from the logs or the admin page --> * Bitwarden_rs version: 1.14.2-1aa5e0d4 <!-- How the server was installed: Docker image / package / built from source --> * Install method: Docker * Clients used: <!-- if applicable --> * Reverse proxy and version: <!-- if applicable --> * Version of mysql/postgresql: <!-- if applicable --> * Other relevant information: ### Steps to reproduce <!-- Tell us how to reproduce this issue. What parameters did you set (differently from the defaults) and how did you start bitwarden_rs? --> ### Expected behaviour <!-- Tell us what should happen --> "Server installed" and "server latest" should be the same ### Actual behaviour <!-- Tell us what happens instead --> Server Installed: 1.14.2-1aa5e0d4 Server Latest: 1.15.0-1aa5e0d4 ### Relevant logs <!-- Share some logfiles, screenshots or output of relevant programs with us. --> ![bwrs](https://user-images.githubusercontent.com/59669357/83528634-59c0cf00-a4b7-11ea-9534-9a844c3c6c96.png)
OVERLORD commented 2025-10-09 17:26:08 +03:00
Author
Owner
Copy Link

@Skaronator commented on GitHub:

Thats because latest doesn't point to 1.15 yet as you can see here: https://hub.docker.com/r/bitwardenrs/server/tags

Not sure which CI Step exactly push these images but I'd wait a few more minutes. The release was only 7 minutes ago as you created this issue.

@Skaronator commented on GitHub: Thats because `latest` doesn't point to 1.15 yet as you can see here: https://hub.docker.com/r/bitwardenrs/server/tags Not sure which CI Step exactly push these images but I'd wait a few more minutes. The release was only 7 minutes ago as you created this issue.
OVERLORD commented 2025-10-09 17:26:08 +03:00
Author
Owner
Copy Link

@giteke commented on GitHub:

The tagged release server:1.15.0 is build already, other architectures are missing still.

The latest tag is special in that it doesn't update with the github tags but with the commits, so it won't see the new version number until there is another commit after the tag was created, but if you have an updated latest, you are on the same commit as the 1.15.0 release, which was built yesterday.

Gotcha

@giteke commented on GitHub: > The tagged release server:1.15.0 is build already, other architectures are missing still. > > The latest tag is special in that it doesn't update with the github tags but with the commits, so it won't see the new version number until there is another commit after the tag was created, but if you have an updated latest, you are on the same commit as the 1.15.0 release, which was built yesterday. Gotcha
OVERLORD commented 2025-10-09 17:26:09 +03:00
Author
Owner
Copy Link

@dani-garcia commented on GitHub:

The tagged release server:1.15.0 is build already, other architectures are missing still.

The latest tag is special in that it doesn't update with the github tags but with the commits, so it won't see the new version number until there is another commit after the tag was created, but if you have an updated latest, you are on the same commit as the 1.15.0 release, which was built yesterday.

@dani-garcia commented on GitHub: The tagged release server:1.15.0 is build already, other architectures are missing still. The latest tag is special in that it doesn't update with the github tags but with the commits, so it won't see the new version number until there is another commit after the tag was created, but if you have an updated latest, you are on the same commit as the 1.15.0 release, which was built yesterday.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
better for forum
bug
bug
bug
documentation
duplicate
enhancement
future Vault
good first issue
help wanted
low priority
notes
pull-request
Mirrored from GitHub Pull Request
 question
SSO
Third party
troubleshooting
troubleshooting
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/vaultwarden#1699
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?