I have just used calver (https://calver.org/ https://calver.org/) to keep it simple - and I use the date[ddmmyyyy]hour,min,second stamps of build time as a mark

I have just used calver (https://calver.org/ https://calver.org/) to keep it simple - and I use the date[ddmmyyyy]hour,min,second stamps of build time as a marker in the version. I have had to deal with the build basically being a recipe of taking multiple ingredients (libs, apps - each with their own lifecycles) and putting'em together in one image to get stuff running. The image version in my case is a tracker of the last-known-good-set (of various ingredients) - as validated by the quick, pre-build tests. I haven't had any major problems till now; may be I am just lucky to not have encountered the hassles w.r.t calver till now. I stumbled upon one similar approach too, recently. https://worklifenotes.com/2020/02/27/automatic-version-increments-with-reliza-hub-2-strategies/ https://worklifenotes.com/2020/02/27/automatic-version-incre...