Since this code is used in production in several projects and we're being careful to avoid breaking changes anyway, it would make sense to tag the code as Version 1 officially. This would also make the breaking changes that we're planning more explicit; they can be published as v2.
After offline chat: Since version 1 is a major version change anyway, we'll put in some deprecation warnings in v0.14.3 and then allow 1.0.0 to break things
Since this code is used in production in several projects and we're being careful to avoid breaking changes anyway, it would make sense to tag the code as Version 1 officially. This would also make the breaking changes that we're planning more explicit; they can be published as v2.