For each module in the wiby.json, retrieve their package.json and determine whether the module is likely to automatically be updated to the new version of your module once it is released.
This could be implemented as a check which needs to be overridden (i.e. only test dependents which would match the current range) or it could just be an option we output as part of results.
Closing this - not really worth pursuing, as there is no automatic way (aside from semantic-release, which obviously is not used by everyone) to determine what the next version of the package will be.
Ref: https://github.com/pkgjs/wiby/blob/master/docs/DRAFT-FLOW.md step 5
This could be implemented as a check which needs to be overridden (i.e. only test dependents which would match the current range) or it could just be an option we output as part of
results
.