> Who's date? The date the customer sees it or the date the developer wrote it? Hopefully you have a continuous deployment pipeline in place, in which the custo

> Who's date? The date the customer sees it or the date the developer wrote it? Hopefully you have a continuous deployment pipeline in place, in which the customer gets an evergreen version without thinking about it, in which case our versioning should be developer centric. This might work for a web page but an app... an app in any kind of environment that tries to control for security (like some large corps)... likely not. And, for server side software.... yeah, not going to do that. This whole thing doesn't work well for shipped software. If you don't like semver for shipped software... there's always something like https://calver.org/ https://calver.org/.