he/him 
I think semver could use a marker for "breaking change to a clearly marked private API that we nonetheless believe people use"
Show this thread
Related problem with semver is how do you mark fixing a bug that has the potential to break because people are relying on the buggy behavior
-
-
Ran into that a lot with
@babeljs when we'd fix non-spec behavior -
When in doubt bump major version. Couldn't hurt.
- 4 more replies
New conversation -
-
-
Bug fixes can go in patch versions. If possible I usually like to deprecate until the next major if I know people are relying on it.
-
It's not always possible and good to call out anyway even if "bugfix"
- 1 more reply
New conversation -
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
In RxJS, we've tried to push most of those to the next major version. It's hard though. Need to draw a line somewhere
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.