[Guardian] Wrong version of Guardian displayed after the last deploy

[data-sync-user]

Important details:

• this was not reproducing after the 1.30 release;

Guardian version:

• v1.30.1;

Steps to reproduce:

1. Load +https://vpn.mozilla.org/version+ / +https://stage-vpn.guardian.nonprod.cloudops.mozgcp.net/version+
2. Observe the version displayed;

Expected result:

• “1.30.1” version is displayed;

Actual result:

• “1.0.0” version is displayed;

Notes:

• See the attached ss;

┆Issue is synchronized with this Jira Bug ┆Reporter: Bianca Hidecuti

[data-sync-user]

➤ Lesley Norton commented:

cc Jeremy Swinarton for priority

[data-sync-user]

➤ Jeremy Swinarton commented:

Looks like for some reason the git binary is no longer available on stage and prod, which is what produces the version number under the hood. It seems to have disappeared around the same time that we changed the Dockerfile to build without dev dependencies, but I’m having trouble seeing how these are related.

cc Jon Buckley and Brandon Wells who may know something about this – I also created https://mozilla-hub.atlassian.net/browse/SVCSE-1409 ( https://mozilla-hub.atlassian.net/browse/SVCSE-1409|smart-link ) to track this.

[data-sync-user]

➤ Valentina Virlics commented:

Santiago Andrigo Jeremy Swinarton it would be helpful for QA to have this fixed, mostly to understand if encountered issues might be Guardian related or not. Or is there another place where we can check the version? Thanks in advance!