Semantic versioning uses MAJOR.MINOR.PATCH numbers to signal the nature and compatibility of software changes: increment MAJOR for incompatible API changes, MINOR for backward-compatible enhancements, and PATCH for backward-compatible bug fixes. section 8.1.5
Originally intended for software packages, semantic versioning can also guide API evolution in distributed systems. Choose versioning practices with the change type and API style in mind. section 8.1.5
API versions can be communicated in different ways:
- Put the major version at the start of a REST API URL path. section 8.1.5
- Include the version in messages published by a messaging-based service. section 8.1.5
A three-part version
Spring Boot 3.5.6 illustrates the MAJOR.MINOR.PATCH format; the example is identified as current at the time of writing. section 8.1.5








