Panduan Perubahan Versi
All of our RESTful APIs start out with only a single version, and you do not need to specify its version number when you call the API.
Semantic Versioning
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 backwards-compatible manner
PATCH version when you make backwards-compatible bug fixes. Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.
A pre-release version MAY be denoted by appending a hyphen (refer to Semantic Versioning - Item 9)
For examples: 1.0.0-alpha.1 is a valid pre-release version.
Last updated