this makes no sense. If you're at 0.1 and you rewrite your own code and break it, by your logic it shouldn't be 0.2 but 1.0 then? What semver is meant to symbo

this makes no sense. If you're at 0.1 and you rewrite your own code and break it, by your logic it shouldn't be 0.2 but 1.0 then? What semver is meant to symbolise is ä that minor and patches from 1.0 forward will remain stable and up until 2.0 during which breakage is to be expected. This means that whatever your project status was at 1.0 should function the same at the minimum level on all versions beginning with 1. This couldn't possibly work if you start counting breaking changes from 0 because right after your first lines of code it's already breaking. You'd have to bump major versions every day.