minor version update breaks compatibility with previous versions

[asklar]

create-react-native-module newest update broke our CI because the --module-name option doesn't exist anymore.
However, npx picks it up since the new version is just a minor update. Ideally we shouldn't have to worry about minor/patch versions breaking due to api/option names incompatibilities

[brodycj]

My understanding of semver is that a 0.x update may have breaking changes. If you use a caret in package.json like "^0.19.0", it should not suddenly pull the 0.20.0 update that I had published. Please quote the appropriate sources if you think this is wrong. Thanks.

[asklar]

@brodybits thanks for replying. Here's the source:
https://semver.org/#summary

[brodycj]

Quoting from https://semver.org/#spec-item-4:

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

Here are a couple of examples from the React Native CHANGELOG itself:

• https://github.com/react-native-community/releases/blob/master/CHANGELOG.md#breaking - breaking changes in React Native 0.64.0
• https://github.com/react-native-community/releases/blob/master/CHANGELOG.md#breaking-1 - breaking changes in React Native 0.63.0

Here is my understanding of how semver is done on npm for 0.x releases:

• for 0.0.z, any update may have breaking changes
• for 0.y.z, a 0.y.0 release may have breaking changes, but a patch release that only increments z should not have breaking changes

Here is how npm documented their use of semver: https://docs.npmjs.com/cli/v6/using-npm/semver