# Version Control Number

**URL:** <https://community.weweb.io/t/version-control-number/14936>\
**Category:** Ask us anything\
**Created:** [December 12, 2024, 1:07pm UTC](https://community.weweb.io/t/version-control-number/14936 "2024-12-12T13:07:48Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![yma](https://avatars.discourse-cdn.com/v4/letter/y/db5fbb/32.png) [@yma](https://community.weweb.io/u/yma)\
**Post date:** [December 12, 2024, 1:07pm UTC](https://community.weweb.io/t/version-control-number/14936/1 "2024-12-12T13:07:48Z")

</div>

I am thinking that weweb can create an automatic version control that I can show somewhere as a variable value in any of the screens because to updating the version every time before deploying is kind a hectic and we miss most of the time to do it

Or introduce a new action called on deploy do XYZ so we can control

---

<div class="post-metadata">

**Author:** ![Joyce](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/joyce/32/13232_2.png) [@Joyce](https://community.weweb.io/u/Joyce)\
**Post date:** [December 17, 2024, 12:22pm UTC](https://community.weweb.io/t/version-control-number/14936/2 "2024-12-17T12:22:11Z")

</div>

Hi @yma 👋

Not sure I understand what you would like to achieve. Is it for example that if you’re publishing the v3 of your application, you would like to display `v3` in the footer of all your pages?

---

<div class="post-metadata">

**Author:** ![yma](https://avatars.discourse-cdn.com/v4/letter/y/db5fbb/32.png) [@yma](https://community.weweb.io/u/yma)\
**Post date:** [December 17, 2024, 12:44pm UTC](https://community.weweb.io/t/version-control-number/14936/3 "2024-12-17T12:44:34Z")

</div>

Yes to be a parameter to be used globally in any page I choose not specifically in all pages, so I can use it in an about page or settings or so, since we are planning to have live and staging and we need to know which version the issue is coming from.

We are also planning to have a chat integration where it shows us the running version of the user to compare which one is that as we might change multiple instances and come back later for example

We have a published v.1.3 and the issue was reported on 1.1 so there are like two versions here gap and we need to trace if this is resolved or not or there is a change happened from our team that maybe plugged this

---

<div class="post-metadata">

**Author:** ![Joyce](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/joyce/32/13232_2.png) [@Joyce](https://community.weweb.io/u/Joyce)\
**Post date:** [December 17, 2024, 12:50pm UTC](https://community.weweb.io/t/version-control-number/14936/4 "2024-12-17T12:50:03Z")

</div>

Got it! I don’t think that info is available in a variable at the moment. Just created a product ticket so the team can look into it. Thanks for the suggestion!

---

<div class="post-metadata">

**Author:** ![Joyce](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/joyce/32/13232_2.png) [@Joyce](https://community.weweb.io/u/Joyce)\
**Post date:** [December 17, 2024, 4:24pm UTC](https://community.weweb.io/t/version-control-number/14936/5 "2024-12-17T16:24:07Z")

</div>

Ah! It turns out it is possible after all 😀

You can get the version of the published app with this code snippet in a formula: `window.wwg_cacheVersion`

 ![CleanShot 2024-12-17 at 17.22.11](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/3/3a5ace63483a54fa5425e0ebd652566a67f1d0ac.png)

Note that it will say `undefined` in the editor but the version number will appear on the published app 🙂