Breaking changes

Versioning

The version numbers indicate the level of changes in each release. Semantic versioning describes how the version numbers are created regarding the impact of updating.

Deprecation policy

When SDX intends to remove a feature from the API or exported files, it will be marked as deprecated in the code if possible. It will also be mentioned in the release notes or in the documentation.

The deprecation period will be half a year. The deprecation can happen in any release. It will technically stay in the code in this period. The removal will only be part of a major release.

Breaking change policy

Breaking change requires you to do work because the state after it is not backward compatible with the state before it. We will always provide instructions on how to solve the breaking changes in the release notes.

If we are forced to make an unplanned breaking change due to something unforeseen, we will release it as a major version, but we will still support the previous major version for half a year.