Output should include suggested version e.g "0.4.1" -> "0.5.0" because breaking changes. Caveats:
contextualized by what that base semver tag is - if it’s a pre-1.0.0 tag, then the rules are different (basically we should treat this with just shifting right - what would normally have been a major change becomes minor, minor becomes patch, patch stays patch) and
if the latest is a prerelease, then just pick the “next” prerelease, if we can. The semantics of alpha/beta/rc are not actually a part of the semver spec, and so dep’s semver lib doesn’t encode anything first-class about them
Output should include suggested version e.g "0.4.1" -> "0.5.0" because breaking changes. Caveats: