Huh? Which ecosystem advocates automatic updates and doesn't allow locking the version numbers of the dependencies until a developer manually updates them?
Of course there will be lots of pain, it just takes one package to slightly violate SemVer and you'll have to hunt down the culprit.
What surprises me is that in the article they seem to think that switching to another versioning scheme will help with this problem. Especially as better tools would mitigate most of this problem.