I have a library which parses via RegEx. The RegEx has been updated, and could be a breaking change for a user. However Elm diff considers this to be patch. I think it should be a major change and communicate this via the version number.
Is there a way to force publish a major version change?
I have manually adjusted the elm.json to be an 8.0 version (elm bump wants a 7.0.1). On publish Elm checks the versions, the output below.
âś— Version 8.0.0 is not correct!
-- INVALID VERSION ---------------------------------------------------- elm.json
Your elm.json says the next version should be 8.0.0, indicating a MAJOR change
to the public API. This does not match the API diff given by:
elm diff 7.0.0
If you have a breaking change that isn’t an API change then I recommend making it an API change. This will solve your releasing problem while also allowing the compiler to help consumers of the package identify the breakage when they upgrade.