Question T12085
Visible to All Users

Breaking changes on minor versions

created 2 years ago

Hello,

We see on recent versions of SurveyJS that there are API changes and Breaking changes on minor versions
The 1.9.69 includes 7 API Changes
The 1.9.73 contains a Breaking Change
We are including SurveyJS considering Semantic Versioning (https://semver.org/) in order to retrieve Patch to make the product more stable, but the patch field is also used for major updates. We would like to know if you are going to solve the versionning problem ?

Thanks for your support.

Answers approved by surveyjs Support

created 2 years ago (modified 2 years ago)

Hello,
Unfortunately, we do not currently follow the Semver versioning MAJOR.MINOR.PATCH pattern.

SurveyJS library updates are shipped on a weekly basis. We aim at minimizing changes which may potentially break existing functionality. In case of API changes, we always preserve the original API (e.g. function/property) name thus making a new update backward compatible.
Still, no one would ague that it is almost impossible to completely avoid such changes in active development. If a change introduced in a maintenance update actually breaks your application code or requires API refactoring, please do let us know. We are always ready to handle this.

We will definitely revisit versioning in our libraries in the future. Thank you for your suggestion.

Please feel free to contact us if you have further assistance.