Note: If you introduce a change that breaks a package dependency, we strongly recommend incrementing the version major number; see below for details.
Incrementing semantic versions in published packages
To help developers who rely on your code, we recommend starting your package version at 1.0.0 and incrementing as follows:
Start with 1.0.0
Backward compatible bug fixes
Increment the third digit
Backward compatible new features
Increment the middle digit and reset last digit to zero
Changes that break backward compatibility
Increment the first digit and reset middle and last digits to zero
Using semantic versioning to specify update types your package can accept
You can specify which update types your package can accept from dependencies in your package's package.json file.
For example, to specify acceptable version ranges up to 1.0.4, use the following syntax: