Publish a major version

[alexei]

If you change public API like e.g. v3.2.9...v3.2.10#diff-58ecd603ddbef47708eeb5b6c2f6705e1402cf43e64acae10766a8131796ddc3L192 you should publish a major version.

[Cito]

These changes correspond to upstream GraphQL.js changes between their minor releases 16.10 and 16.13:

• Core 3.2.9 = JS 16.10.0
• Core 3.2.10 = JS 16.13.0

We follow their versioning semantics with the difference that their major versions are our minor versions, and their minor versions are our patch version. So breaking changes can happen in minor releases - this is documented in our README.

However, we leave it to upstream to decide what is considered a breaking change. In this case, the change was in a minor release upstream, so it wasn't considered breaking upstream.

You can consider it a bad decision, but changing our long-year versioning policy would create even more confusion.

If you think the change between 16.10.0 and 16.13.0 should have been ported in a different way, let me know how.