Those version numbers look way too similar to dates!!

What (user) invisible said. year.week or year.week.patch if there has been a patch. And there's a build number after that. We're on 4fbcc4b942a8, probably the prefix of a git hash I'm guessing. But then there's kind of a marketing version number as well, for which we are currently on v10.0 or v10. something:

https://www.teslarati.com/tesla-v10-wide-release-mobile-app-...

Those versions are more like the true major release versions, whereas the date versions are inside of that and are minor releases.

Thanks all, but I wasn't asking for help parsing it, rather critiquing it as a poor version formatting choice bc of its ambiguity.

Yes that’s a valid critique, and one I agree with. I added my comment more as an elaboration for anyone else interested in more.

They are in this format: Year.Week.Patch

It seems to generally follow the format of Year.Version.Patch.