[GH-ISSUE #252] Please add docker tag for vault v2.5.0, not latest #128

New issue

Closed

opened 2026-03-03 01:25:33 +03:00 by kerem · 3 comments

kerem commented

2026-03-03 01:25:33 +03:00

Owner

Originally created by @ghost on GitHub (Nov 15, 2018).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/252

Current 1.4.0 docker tag has v2.4.0 web vault
Current latest docker tag has v2.5.0 web vault

Could you add 1.4.1 or 1.5.0 tag for docker image for web vault v2.5.0, I don't want to use latest tag because it is not recommended and after some time you don't now which version you are using in your env but I want to use features from v2.5.0.

Originally created by @ghost on GitHub (Nov 15, 2018). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/252 Current 1.4.0 docker tag has v2.4.0 web vault Current latest docker tag has v2.5.0 web vault Could you add 1.4.1 or 1.5.0 tag for docker image for web vault v2.5.0, I don't want to use latest tag because it is not recommended and after some time you don't now which version you are using in your env but I want to use features from v2.5.0.

kerem closed this issue

2026-03-03 01:25:33 +03:00

kerem commented

2026-03-03 01:25:34 +03:00

Author

Owner

@strayer commented on GitHub (Nov 15, 2018):

As far as I can see, the latest tag is simply an automated build for the master branch. There is no release yet with Vault 2.5.0, but surely one will come when it is ready.

See automated build details on Docker Hub for more information.

@strayer commented on GitHub (Nov 15, 2018): As far as I can see, the latest tag is simply an automated build for the master branch. There is no release yet with Vault 2.5.0, but surely one will come when it is ready. See [automated build details](https://hub.docker.com/r/mprasil/bitwarden/builds/) on Docker Hub for more information.

kerem commented

2026-03-03 01:25:34 +03:00

Author

Owner

@mprasil commented on GitHub (Nov 15, 2018):

Yes that's correct. We do aim to have master (latest image) in usable state though and any major development is done in separate branch. (with beta images)

So if you're okay with running that version, @Haxy89, then fell free to use latest, it should work fine and any bugs are mostly related to new vault functionality and usually fixed quite fast. I'm personally using latest.

If you'd rather use versioned release, that's also fine. We do those quite often. The vault 2.5.0 version isn't quite there yet, to do a versioned release, we just got it to a stage where it works enough to merge to master, but some functionality isn't implemented yet.

@mprasil commented on GitHub (Nov 15, 2018): Yes that's correct. We do aim to have master (latest image) in usable state though and any major development is done in separate branch. (with beta images) So if you're okay with running that version, @Haxy89, then fell free to use latest, it should work fine and any bugs are mostly related to new vault functionality and usually fixed quite fast. I'm personally using latest. If you'd rather use versioned release, that's also fine. We do those quite often. The vault 2.5.0 version isn't quite there yet, to do a versioned release, we just got it to a stage where it works enough to merge to master, but some functionality isn't implemented yet.

kerem commented

2026-03-03 01:25:34 +03:00

Author

Owner

@mprasil commented on GitHub (Nov 15, 2018):

I'm going to close this issue as we don't need issue reminding us to release new version - we do that as part of normal development. :D

@mprasil commented on GitHub (Nov 15, 2018): I'm going to close this issue as we don't need issue reminding us to release new version - we do that as part of normal development. :D

kerem referenced this issue

2026-03-03 02:20:03 +03:00

[PR #128] [MERGED] Return revision date in miliseconds (fixes #127) #2618