Would you want crates.io/cargo publish to enforce strictly correct SemVer conventions?

I've recently had to fix up one of my projects which suddenly broke and no longer compiled.

The reason for the breakage was that a definiton of a symbol was removed from the library I've been using and at the same time only the Patch part of the crate version was incremented. Meaning I pulled the crate using 0.3.\* and with 0.3.0 it compiled, but the newly published version 0.3.1 broke the build.

In my case it wasn't so bad and an easy fix was fast to write, but it got me thinking of how much of a problem this is for the wider ecosystem. Some searching showed me, that of course there is a tool rust-semverver to do exactly that. Sadly it errors on my system (or maybe im just using it wrong). Would've been interesting to see how often this actually happens on crates.io and how much of a problem this really is.

Do you guys have problems with this? Or is this a niche case you barley ever worry about?