Version numbering
Loris releases follow the semantic versioning scheme of MAJOR.MINOR.PATCH. This primarily means that
- the MAJOR version number is bumped to signify that backwards-incompatible API (or CLI) changes have been introduced,
- the MINOR version number is bumped when backwards-compatible feature sets or other changes have been introduced, and
- the PATCH version number is bumped whenever backwards-compatible bug fixes are introduced.
Asserting Loris version compatibility
The procedure (platform:assert-version MAJOR MINOR PATCH) may be used to ensure your program is built with a compatible version of Loris. If applied to a version number set that the underlying Loris library is not backwards (or forwards) compatible with, the program will exit with an error.