I just merged some PRs to jscodeshift-add-imports and jscodeshift-find-imports to silence peer dependency warnings on jscodeshift. We decided to set the peer dep version to "jscodeshift": ">=0.7 <1", which isn't great, but it seems like the only reasonable thing we can do if we're not going to update the peer dep every time jscodeshift releases a new 0.x version.

Aside from the fundamental problems with using 0.x versioning on a widely used library, it's not even clear from the changelog here if there are any breaking changes from one 0.x version to another. I can't tell what the rationale for bumping the minor or patch version number is here.

In any case, having >=1.x semantic versioning would reduce the friction for library authors and end users in dealing with future changes to jscodeshift.

Releasing a v1 doesn't have to mean you're declaring jscodeshift stable or unlikely to have breaking changes soon. You could officially disclaim that in the README. It would just be a promise that future 1.x versions (if you do release any before 2.x) have no breaking changes.