Consider releasing at least one minor version of this crate

[brannondorsey]

By publishing only releases versioned 0.0.z you are unable to publish a new version that includes non-breaking changes.

This prevents users of this crate from receiving such non-breaking updates via cargo update unless cargo update -Zunstable-options --breaking is specified.

If you instead cut the next release as 0.x.0 you would give yourself the ability (but not the obligation) to publish non-breaking changes to this crate that could be immediately adopted the next time a user runs a routine cargo update.