I have possible breaking change for a npm package, the version was 0.0.15, what version should i use now

In semantic versioning, if you introduce a breaking change, you typically increment the major version number. However, your package is currently at version 0.0.15, which suggests that it is still in initial development and not yet stable.

In semantic versioning, versions are denoted as MAJOR.MINOR.PATCH. For packages with a version number starting with 0, the major version is considered 0, and changes in MINOR can be used to indicate breaking changes because the package is still in development. Here’s how you might proceed:

• If you want to signal that this is a breaking change while the package is still in development, you should increment the MINOR version. So, you would go from 0.0.15 to 0.1.0.

Once your package reaches a stable release (typically 1.0.0), you would then start incrementing the MAJOR version for breaking changes, MINOR for backward-compatible features, and PATCH for backward-compatible bug fixes.