# Should the version # on the website match the release # on github?

**URL:** <https://vaultwarden.discourse.group/t/should-the-version-on-the-website-match-the-release-on-github/1057>\
**Category:** Help\
**Created:** [August 9, 2021, 9:30pm UTC](https://vaultwarden.discourse.group/t/should-the-version-on-the-website-match-the-release-on-github/1057 "2021-08-09T21:30:28Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![elfensky](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/elfensky/32/307_2.png) [@elfensky](https://vaultwarden.discourse.group/u/elfensky)\
**Post date:** [August 9, 2021, 9:30pm UTC](https://vaultwarden.discourse.group/t/should-the-version-on-the-website-match-the-release-on-github/1057/1 "2021-08-09T21:30:28Z")

</div>

I have been trying to upgrade to the latest Vaultwarden release - 2.22.2, however either I’m doing something wrong or you guys forgot to update the version number in the footer of the website.

I deleted and re-downloaded Vaultwarden’s docker image using the :latest tag, and when ran, the website shows version 2.21.1

 ![image](https://global.discourse-cdn.com/free1/uploads/vaultwarden/original/1X/290746fed3b95a01dcd81e33564c115605f84029.png)

I thought - huh weird, maybe my vps provider uses an internal docker cache or something, so I downloaded the image using the :2.22.2 tag, so I specifically get the new version.

When I run it however, the website still shows as running version 2.21.1.

Now, my question is - is it me doing something wrong, or should I go report this on github?

---

<div class="post-metadata">

**Author:** ![BlackDex](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/blackdex/32/8_2.png) [@BlackDex](https://vaultwarden.discourse.group/u/BlackDex)\
**Post date:** [August 9, 2021, 9:44pm UTC](https://vaultwarden.discourse.group/t/should-the-version-on-the-website-match-the-release-on-github/1057/2 "2021-08-09T21:44:36Z")

</div>

The latest version of vaultwarden is v1.22.2, and the latest web-vault available is v.2.21.1 which currently is compatible with Vaultwarden. So everything is correct.

You misread the v1.xx.x of the vaultwarden version as v2.xx.x.