Upgrade path from testing branch

[Brandon-Access-Memory]

I have been running the Testing branch of VW via Docker Swarm for sometime and utilising the SSO functionality really successfully I might add but I'm wondering, with merging of OIDC SSO to the main is there a specific upgrade path I need to follow or is it simply a case of pulling the new image?

[BlackDex]

If you were using the testing tagged Vaultwarden images from this repo, then switching to latest will work just fine.

If you were using any other provided image, I'm not sure.

[Brandon-Access-Memory]

Thank you @BlackDex!

[ivanlinares]

Hi! I'm coming from community-scripts and this is my version:

Vaultwarden:~# vaultwarden -v
Vaultwarden 1.34.3-r1
Web-Vault Version file missing

how can I update my install? Thanks in advance

[BlackDex]

You need to check via your tooling how you installed Vaultwarden, and i guess it's Alpine based, so you need to wait for Alpine to update it.

[pictosun]

Alpine Linux doesn't have the actual version? Is this something because something went wrong from Vaultwarden's side, or is it simply not an updated image at Alpine?
https://pkgs.alpinelinux.org/package/edge/community/x86/vaultwarden

[BlackDex]

This project does not maintain any third-party package. We only build container images which are published via GitHub, Quay and Docker Hub.

All other packages via any other form are not handled by this project.

So, i this case, someone at Alpine needs to update the build package.

[pictosun]

Thanks for your feedback.