I think it's time to move to 1.0+ versioning so that we can actually use the version number to transmit meaningful semantic information (ie. that a "major" version bump is a compatibility-breaking change). Our current version numbers (of the form v0.x.y) transmit basically nothing, because:
Major version zero (0.y.z) is for initial development. Anything may change at any time.
This entry from the Semver FAQ is also helpful:
How do I know when to release 1.0.0?
If your software is being used in production, it should probably already be 1.0.0. If you have a stable API on which users have come to depend, you should be 1.0.0. If you’re worrying a lot about backwards compatibility, you should probably already be 1.0.0.
I think all of those apply to this package, so let's do it with the next release.
Anything blocking 1.0.0 for this project? Seems it is widely used in production at the point.
I'd like to quote the argument directly from this post on a different project (https://github.com/graphql/graphql-js/issues/1005):
See also https://0ver.org/
Best.