[SOLVED] Build number is not in semver format

Summary
I see warning messages in the Mattermost LOG and the server ABOUT screen does not show the correct version.

Steps to reproduce
Following the upgrade instructions at Upgrade Mattermost — Mattermost documentation in a standard Mattermost installation using .tar.gz

I perform the next UPGRADE PATH: 7.7.1 → 7.8.14 (ESR) → 8.1.5 (ESR) using the lastest .tar.gz releases available at this time

wget https://releases.mattermost.com/7.8.14/mattermost-7.8.14-linux-amd64.tar.gz
wget https://releases.mattermost.com/8.1.5/mattermost-8.1.5-linux-amd64.tar.gz

Expected behavior
The ABOUT window shows the correct version, and no associated warn msg shows in mattermost.log

Observed behavior

AT mattermost.log

{"timestamp":"2023-11-07 22:33:18.376 -06:00","level":"info","msg":"Current version is 8.1.5 (6772745529/Mon Nov  6 15:22:11 UTC 2023/f8f79e13ef11d5bd2527d21a1967bd37f46a0fae/e33941bd63a35f71153c8035608dd8904d1bf305)","caller":"app/server.go:426","current_version":"8.1.5","build_number":"6772745529","build_date":"Mon Nov  6 15:22:11 UTC 2023","build_hash":"f8f79e13ef11d5bd2527d21a1967bd37f46a0fae","build_hash_enterprise":"e33941bd63a35f71153c8035608dd8904d1bf305","service_environment":"production"}
{"timestamp":"2023-11-07 22:33:18.376 -06:00","level":"info","msg":"Enterprise Build","caller":"app/server.go:436","enterprise_build":true}
{"timestamp":"2023-11-07 22:33:18.376 -06:00","level":"info","msg":"Printing current working","caller":"app/server.go:442","directory":"/opt/mattermost-broken_7814_815_7814/logs"}
{"timestamp":"2023-11-07 22:33:18.376 -06:00","level":"info","msg":"Loaded config","caller":"app/server.go:443","source":"file:///opt/mattermost-broken_7814_815_7814/config/config.json"}
{"timestamp":"2023-11-07 22:33:18.379 -06:00","level":"info","msg":"Starting workers","caller":"jobs/workers.go:48"}
{"timestamp":"2023-11-07 22:33:18.379 -06:00","level":"info","msg":"Starting schedulers.","caller":"jobs/schedulers.go:47"}
...
..
.
{"timestamp":"2023-11-07 22:34:50.033 -06:00","level":"info","msg":"Starting Server...","caller":"app/server.go:913"}
{"timestamp":"2023-11-07 22:34:50.033 -06:00","level":"info","msg":"Server is listening on [::]:8065","caller":"app/server.go:989","address":"[::]:8065"}
{"timestamp":"2023-11-07 22:35:13.586 -06:00","level":"info","msg":"Post.Message has size restrictions","caller":"sqlstore/post_store.go:2558","max_characters":16383,"max_bytes":65535}
{"timestamp":"2023-11-07 22:35:20.033 -06:00","level":"warn","msg":"Build number is not in semver format","caller":"app/product_notices.go:100","build_number":""}
{"timestamp":"2023-11-07 22:35:20.033 -06:00","level":"warn","msg":"Build number is not in semver format","caller":"app/product_notices.go:100","build_number":""}
{"timestamp":"2023-11-07 22:35:20.033 -06:00","level":"warn","msg":"Build number is not in semver format","caller":"app/product_notices.go:100","build_number":""}

Screenshot

Our DevOps team is looking into this. Please follow status updates on this here: After upgrading to 9.1.2, the Mattermost version does not appear in the console. · Issue #25335 · mattermost/mattermost · GitHub.