Clarify aerich package versioning rules

[leshark]

Hello, I have spotted that in version v0.7.0 not backward compatible changes were made:

Now aerich use .py file to record versions.

According to semver this should be a breaking change as generated sql file can be used somewhere else (changing them to .py files may break something + linters that lint .sql files will also break)

Not advocating for or against new functionality, however such a big change is usually not expected when updating a minor version. Can you consider switching to semver or at least explicitly clarify versioning rules so more precise constraints can be used when updating aerich?

[Molkree]

such a big change is usually not expected when updating a minor version

Because it's still v0.y.z it's in line with semver:

Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.

link

Of course, it would be ideal if projects matured to v1 in 3 years and 37 releases :)

[leshark]

@Molkree let's use ZeroVer then