Version number not shown in the app

[russdeffner]

Is your feature request related to a problem? Please describe. When filling out a bug report it asks you to provide the version # of the Tasking Manager - but that information is not always easy to find.

Describe the solution you'd like On the About Page (or other logical place to find such information), the current version number of the Tasking Manager should be easily discoverable.

Describe alternatives you've considered It is not too hard to find this on GitHub, however - if it is a bug discovered on another installation of the Tasking Manager, such as the Staging Site, it would be best to have the version in the app. Also for those not familiar with GitHub or filing a report via the Support form instead of GitHub the version number may not be known at all (which is also not asked on the form at the moment FYI).

The footer of the TM 'landing page' could be another good spot for version #.

[HelNershingThapa]

Hello, @russdeffner. We regret that you had to go through this. Please refer to the repository's releases section until we find a good location for displaying the version number on the Tasking Manager app.

[Patrik-Br]

Agree with Rusell. Especially at this moment since there had been released a new version of TM (v4.5.2) but because of the turkey/syria earthquake response the live version is still 4.5.1.

[ramyaragupathy]

@mahesh-naxa to investigate further on https://commitizen-tools.github.io/commitizen/ cc @dakotabenjamin @eternaltyro @spwoodcock

[dakotabenjamin]

Aside but the servers do have the git commit hash of the running version of TM as an environment variable. Could be useful?

[spwoodcock]

This would be partly solved by adding the Dockerflow endpoints we discussed @dakotabenjamin @eternaltyro

The endpoint would be /__version__ , example in FMTM: https://api.dev.fmtm.hotosm.org/__version__

But it's only on the API / backend.

Another approach to display in the frontend could be to hardcode the current version in a file somewhere, and increment it with commitzen when the version changes. @ramyaragupathy @mahesh-naxa commitzen can increment a version number in any file (it uses regex). Example config from FMTM pyproject.toml file:

version_files = [
    "pyproject.toml:version",
    "app/__version__.py",
    "../frontend/package.json:version",
    "../../chart/Chart.yaml:appVersion",
]

Before the colon is the file, after the colon is the key to update. You could probably even have the version in a .jsx file, set as a variable like:

const appVersion = 4.10.0