Software using Semantic Versioning MUST declare a public API.įor some kinds of projects, where you don’t have any kind of API to be consumed by other clients, the MAJOR version probably doesn’t make sense. The first item on the Semantic Versioning specification says: For example, in Gradle projects is usual to use -SNAPSHOT during the development phase and remove that classifier when releasing the project.

You can use these version classifiers to quickly identify the kind of version of your project and avoid confusion between a pre-release and a release version. A pre-release version may be denoted by appending a version classifier that starts with a. PATCH version when you make backwards-compatible bug fixes.Īn important concept defined by Semantic Versioning is the pre-release version.MINOR version when you add functionality in a backwards-compatible manner, and.MAJOR version when you make incompatible API changes,.X is the major version, Y is the minor version, and Z is the patch version. You can read all the specifications here.Ī normal version number MUST take the form X.Y.Z where X, Y, and Z are non-negative integers, and MUST NOT contain leading zeroes.

The Semantic Versioning specification consists of a couple of conventions to assign and increment version numbers to your software.

Android gradle plugin update