mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2025-12-09 17:23:04 +03:00
Please add docker tag for vault v2.5.0, not latest #2286
Reference in New Issue
Block a user
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?
Originally created by @ghost on GitHub.
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.
@mprasil commented on GitHub:
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
@strayer commented on GitHub:
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.
@mprasil commented on GitHub:
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.