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.
-
There's massive momentum required for a major version bump. People seldom upgrade outside of majors.
- 3 more replies
New conversation -
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.