Enforce that each `compatibility` entry has a different major version
ehmicky opened this issue · 1 comments
ehmicky commented
Due to the compatibility field being used for version pinning and due to the fact that version pinning is major-version-based, the current algorithm requires each compatibility entry to have a different major version.
We should validate this as part on our existing automated tests.
Please note that, according to semver, the "major version" should be the second number for 0.*.* versions and the third number for 0.0.* versions.