Non-semantic version numbers

[Roy-Orbison]

Can you please use semantic version numbers? Going from v2.2 to v2.2.0.1 doesn't explain much, and we can't know if, say, going up to v2.2.1 is an increase in functionality that integrations may have to deal with, or if it's only a bug-fix.

From semver.org:

Given a version number MAJOR.MINOR.PATCH, increment the:

MAJOR version when you make incompatible API changes
MINOR version when you add functionality in a backward compatible manner
PATCH version when you make backward compatible bug fixes

Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.

Always using those 3 numbers makes it clear what's going on.