Update the major version number for breaking changes
aalex opened this issue · comments
Update the major version number for breaking changes
In 0.4.0, a breaking has been introduced: the support for null safety. The version number should have been incremented to 1.0.0, according to Semantic Versioning 2, if you follow it. (all Dart packages should)
Hi @aalex 👋
Thanks for opening an issue!
Although semantic versioning doesn’t promise any compatibility between versions prior to 1.0.0, the Dart community convention is to treat those versions semantically as well. The interpretation of each number is just shifted down one slot: going from 0.1.2 to 0.2.0 indicates a breaking change, going to 0.1.3 indicates a new feature, and going to 0.1.2+1 indicates a change that doesn’t affect the public API. For simplicity’s sake, avoid using + after the version reaches 1.0.0.
https://dart.dev/tools/pub/versioning#semantic-versions
In this case going from 0.3.0 to 0.4.0 indicates a breaking change since the package is <1.0.0. Hope that helps 👍
Oh, ok! Since the version is <1.0.0, it works. Thanks for your answer!