github-starred/vaultwarden
2
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-07-18 01:49:32 -05:00
Code Issues 498 Packages Projects Releases 83 Wiki Activity

[GH-ISSUE #5867] Missing exact release version in Cargo.toml for each tag. #35219

New Issue
Closed
opened 2026-07-13 20:00:52 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-07-13 20:00:52 -05:00
Owner
Copy Link

Originally created by @tglman on GitHub (May 18, 2025).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/5867

Vaultwarden Support String

not sure about this

Vaultwarden Build Version

Deployment method

Other method

Custom deployment method

No response

Reverse Proxy

Host/Server Operating System

Other

Operating System Version

No response

Clients

Desktop

Client Version

No response

Steps To Reproduce

All the release tag have the exact same version (1.0.0) in the Cargo.toml, it will be useful to have the exact version of the tag in it, obviously I'm asking that only for future releases.

let me know if there are any issues with that.

Expected Result

exact version

Actual Result

no version

Logs

Screenshots or Videos

No response

Additional Context

No response

Originally created by @tglman on GitHub (May 18, 2025). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/5867 ### Vaultwarden Support String not sure about this ### Vaultwarden Build Version * ### Deployment method Other method ### Custom deployment method _No response_ ### Reverse Proxy * ### Host/Server Operating System Other ### Operating System Version _No response_ ### Clients Desktop ### Client Version _No response_ ### Steps To Reproduce All the release tag have the exact same version (1.0.0) in the Cargo.toml, it will be useful to have the exact version of the tag in it, obviously I'm asking that only for future releases. let me know if there are any issues with that. ### Expected Result exact version ### Actual Result no version ### Logs ```text ``` ### Screenshots or Videos _No response_ ### Additional Context _No response_
GiteaMirror added the bug label 2026-07-13 20:00:52 -05:00
GiteaMirror commented 2026-07-13 20:00:54 -05:00
Author
Owner
Copy Link

@BlackDex commented on GitHub (May 18, 2025):

This is intended. We do not use this specific value for versioning Vaultwarden.

<!-- gh-comment-id:2889235993 --> @BlackDex commented on GitHub (May 18, 2025): This is intended. We do not use this specific value for versioning Vaultwarden.
GiteaMirror commented 2026-07-13 20:00:54 -05:00
Author
Owner
Copy Link

@tglman commented on GitHub (May 19, 2025):

Hi,

Thanks for the reply, do you have somewhere documented the reason for it ?

Thanks in advance

<!-- gh-comment-id:2889296920 --> @tglman commented on GitHub (May 19, 2025): Hi, Thanks for the reply, do you have somewhere documented the reason for it ? Thanks in advance
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 bug
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#35219
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?