github-starred/vaultwarden
2
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-07-15 10:02:09 -05:00
Code Issues 479 Packages Projects Releases 83 Wiki Activity

Release 1.15.0 shows wrong version number #4357

New Issue
Closed
opened 2026-03-07 19:41:53 -06:00 by GiteaMirror · 7 comments
GiteaMirror commented 2026-03-07 19:41:53 -06:00
Owner
Copy Link

Originally created by @restonica on GitHub (Jun 2, 2020).

Wrong displayed version for 1.15.0

Environment

Logs from last 1.15.0 version

Expected behaviour

Version 1.15.0-?aa5e0d4

Actual behaviour

Version 1.14.2-1aa5e0d4

Originally created by @restonica on GitHub (Jun 2, 2020). ### Wrong displayed version for 1.15.0 ### Environment Logs from last 1.15.0 version ### Expected behaviour Version 1.15.0-?aa5e0d4 ### Actual behaviour Version 1.14.2-1aa5e0d4
GiteaMirror commented 2026-03-07 19:41:54 -06:00
Author
Owner
Copy Link

@tomamplius commented on GitHub (Jun 3, 2020):

seem Ok from last release Version 1.15.0.

Jun  3 04:41:14 bitwarden systemd[1]: Started Bitwarden Server (Rust Edition).
Jun  3 04:41:14 bitwarden bitwarden_rs[26359]: /--------------------------------------------------------------------\
Jun  3 04:41:14 bitwarden bitwarden_rs[26359]: |                       Starting Bitwarden_RS                        |
Jun  3 04:41:14 bitwarden bitwarden_rs[26359]: |                           Version 1.15.0                           |
Jun  3 04:41:14 bitwarden bitwarden_rs[26359]: |--------------------------------------------------------------------|
Jun  3 04:41:14 bitwarden bitwarden_rs[26359]: | This is an *unofficial* Bitwarden implementation, DO NOT use the   |
Jun  3 04:41:14 bitwarden bitwarden_rs[26359]: | official channels to report bugs/features, regardless of client.   |
Jun  3 04:41:14 bitwarden bitwarden_rs[26359]: | Send usage/configuration questions or feature requests to:         |
Jun  3 04:41:14 bitwarden bitwarden_rs[26359]: |   https://bitwardenrs.discourse.group/                             |
Jun  3 04:41:14 bitwarden bitwarden_rs[26359]: | Report suspected bugs/issues in the software itself at:            |
Jun  3 04:41:14 bitwarden bitwarden_rs[26359]: |   https://github.com/dani-garcia/bitwarden_rs/issues/new           |
Jun  3 04:41:14 bitwarden bitwarden_rs[26359]: \--------------------------------------------------------------------/
Jun  3 04:41:14 bitwarden bitwarden_rs[26359]: Running migration 20200409235005
Jun  3 04:41:19 bitwarden bitwarden_rs[26359]: [2020-06-03 04:41:19][ws][INFO] Listening for new connections on 0.0.0.0:3012.
Jun  3 04:41:19 bitwarden bitwarden_rs[26359]: [2020-06-03 04:41:19][start][INFO] Rocket has launched from http://0.0.0.0:8000
Jun  3 08:14:11 bitwarden bitwarden_rs[26359]: [2020-06-03 08:14:11][ws::io][INFO] Accepted a new tcp connection from 10.0.0.104:41474.
@tomamplius commented on GitHub (Jun 3, 2020): seem Ok from last release Version 1.15.0. ~~~ Jun 3 04:41:14 bitwarden systemd[1]: Started Bitwarden Server (Rust Edition). Jun 3 04:41:14 bitwarden bitwarden_rs[26359]: /--------------------------------------------------------------------\ Jun 3 04:41:14 bitwarden bitwarden_rs[26359]: | Starting Bitwarden_RS | Jun 3 04:41:14 bitwarden bitwarden_rs[26359]: | Version 1.15.0 | Jun 3 04:41:14 bitwarden bitwarden_rs[26359]: |--------------------------------------------------------------------| Jun 3 04:41:14 bitwarden bitwarden_rs[26359]: | This is an *unofficial* Bitwarden implementation, DO NOT use the | Jun 3 04:41:14 bitwarden bitwarden_rs[26359]: | official channels to report bugs/features, regardless of client. | Jun 3 04:41:14 bitwarden bitwarden_rs[26359]: | Send usage/configuration questions or feature requests to: | Jun 3 04:41:14 bitwarden bitwarden_rs[26359]: | https://bitwardenrs.discourse.group/ | Jun 3 04:41:14 bitwarden bitwarden_rs[26359]: | Report suspected bugs/issues in the software itself at: | Jun 3 04:41:14 bitwarden bitwarden_rs[26359]: | https://github.com/dani-garcia/bitwarden_rs/issues/new | Jun 3 04:41:14 bitwarden bitwarden_rs[26359]: \--------------------------------------------------------------------/ Jun 3 04:41:14 bitwarden bitwarden_rs[26359]: Running migration 20200409235005 Jun 3 04:41:19 bitwarden bitwarden_rs[26359]: [2020-06-03 04:41:19][ws][INFO] Listening for new connections on 0.0.0.0:3012. Jun 3 04:41:19 bitwarden bitwarden_rs[26359]: [2020-06-03 04:41:19][start][INFO] Rocket has launched from http://0.0.0.0:8000 Jun 3 08:14:11 bitwarden bitwarden_rs[26359]: [2020-06-03 08:14:11][ws::io][INFO] Accepted a new tcp connection from 10.0.0.104:41474. ~~~
GiteaMirror commented 2026-03-07 19:41:54 -06:00
Author
Owner
Copy Link

@timendum commented on GitHub (Jun 3, 2020):

The issue is in the admin/diagnostics page:

screenshot

@timendum commented on GitHub (Jun 3, 2020): The issue is in the admin/diagnostics page: ![screenshot](https://user-images.githubusercontent.com/670620/83617768-d7eda600-a589-11ea-91ac-15c862b2b3d0.png)
GiteaMirror commented 2026-03-07 19:41:55 -06:00
Author
Owner
Copy Link

@tomamplius commented on GitHub (Jun 3, 2020):

No issue for me too

2020-06-03_11-11

@tomamplius commented on GitHub (Jun 3, 2020): No issue for me too [![2020-06-03_11-11](https://user-images.githubusercontent.com/6951820/83618623-00c26b00-a58b-11ea-95eb-4be1a3c0950c.png) ](url)
GiteaMirror commented 2026-03-07 19:41:55 -06:00
Author
Owner
Copy Link

@waschinski commented on GitHub (Jun 3, 2020):

When I recreated my docker container and pulled latest I ended up with the same result, Web being up-to-date but Server being still on 1.14.2.

Explicitly pulling the 1.15.0 image did update properly though.

Might have to do with latest image being created 2 days ago while all 1.15.0 images are from about 20 hours ago.

@waschinski commented on GitHub (Jun 3, 2020): When I recreated my docker container and pulled **latest** I ended up with the same result, Web being up-to-date but Server being still on 1.14.2. Explicitly pulling the **1.15.0** image did update properly though. Might have to do with **latest** image being created 2 days ago while all **1.15.0** images are from about 20 hours ago.
GiteaMirror commented 2026-03-07 19:41:56 -06:00
Author
Owner
Copy Link

@restonica commented on GitHub (Jun 3, 2020):

Thanks waschinski.
Indeed just the lastest tag of raspberry image that currently is on 1.14.2

@restonica commented on GitHub (Jun 3, 2020): Thanks waschinski. Indeed just the lastest tag of raspberry image that currently is on 1.14.2
GiteaMirror commented 2026-03-07 19:41:56 -06:00
Author
Owner
Copy Link

@giteke commented on GitHub (Jun 3, 2020):

Explanation is here from a closed issue: https://github.com/dani-garcia/bitwarden_rs/issues/1015#issuecomment-637568561

@giteke commented on GitHub (Jun 3, 2020): Explanation is here from a closed issue: https://github.com/dani-garcia/bitwarden_rs/issues/1015#issuecomment-637568561
GiteaMirror commented 2026-03-07 19:41:57 -06:00
Author
Owner
Copy Link

@restonica commented on GitHub (Jun 3, 2020):

Duplicated with #1015 (comment)

@restonica commented on GitHub (Jun 3, 2020): Duplicated with #1015 (comment)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
better for forum
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
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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