Removing an export from any file is semver-major. Instead, let's include this change in the rewrite branch, so that the rewrite can be v3.

Semver only dictates major releases for breaking changes to the public API, which should be well defined.

For this system to work, you first need to declare a public API. This may consist of documentation or be enforced by the code itself. Regardless, it is important that this API be clear and precise.

Enzyme has a pretty clear public API defined by the documentation, so I would argue this isn't a breaking change since react-compat exports are not defined as part of the public API (and never should be).

Either way, we can close this if we want to consider it semver major since the rewrite branch doesn't contain this import/export anymore.

Our public API is defined as "everything that can possibly be reachable or observed", regardless of what's in documentation, which is also the way I think all projects should define it.

I think that's an ill-defined way to describe a public API, but if that's the standard for Enzyme so be it. In that case, this PR is unnecessary since the same change will be made in #1007