What is a common mistake when working with API versioning strategies?

A common mistake with API versioning strategies is creating a new API version for every internal refactor quickly multiplies maintenance cost without giving clients meaningful contract stability. The safer approach is to design and test the behavior explicitly rather than assuming the platform or dependency will handle it automatically.