Upgrade Issues

[Matohl]

Having updated to 21054 it still states 21053 in MSR although hard refresh in Chromium (Ctrl-F5) and even re-boot. Reading the startup log it runs 21054:

2021-02-24T06:30:51.773Z app:null Reactor application v21054 starting on v14.15.4
2021-02-24T06:30:51.779Z app:INFO Process ID 1801; platform linux/arm #1402 SMP Tue Feb 16 14:12:18 GMT 2021
2021-02-24T06:30:51.818Z default:INFO Module Entity v21025
2021-02-24T06:30:51.825Z Controller:null Module Controller v21054
2021-02-24T06:30:51.827Z default:null Module Structure v21050
2021-02-24T06:30:51.843Z default:null Module Ruleset v21041
2021-02-24T06:30:51.844Z default:null Module Rulesets v21041
2021-02-24T06:30:51.874Z default:null Module Rule v21051
2021-02-24T06:30:51.882Z default:null Module Engine v21054
2021-02-24T06:30:51.884Z default:null Module httpapi v21041
2021-02-24T06:30:51.891Z default:null Module httpproxy v21054
2021-02-24T06:30:51.945Z default:null Module wsapi v21053
...

Probably something I am missing but can not figure out why

[cw-kid]

Same here. I didn't notice your post before I posted about the same issue.

https://smarthome.community/topic/349/updated-to-0-1-21054-but-it-still-says-0-1-21053

[toggledbits]

Not to worry. I haven't spent a lot of time automating the build process, so it's still pretty manual and I have to remember to update the version on the splash/about screen. I'm tired of getting it wrong and probably close to crossing the threshold to getting it automated.

[rafale77]

Maybe automatically use the date as the build number?

[toggledbits]

It does that. What it doesn't do is manipulate the source files to insert the build number. I guess it's time.