MonstercatNet uses the following versioning strategy:
number | description |
---|---|
major | mirrors the version of the supported monstercat api version |
minor | major version according to semver (changes when incompatible API changes were made)) |
build | minor version according to semver (changes when functionality or bugfixes in a backwards compatible manner were added |