If you're getting to a semver of 145.14.7 with Semver then sack your API designer.

Remember the major version bumps when it is not backward compatible. New functionality can be backward compatible.

You can keep older semver APIs working with endpoints that support upgrading the older format to the newer internally, which allows you to enable things like sunsetting API versions to provide automated upgrade notifications.

All I'm saying is that user version numbers are more a marketing exercise than anything logical.