Semantic versioning does not work for PSGallery
Allow new versions of modules to be published according to semantic version.
Without semantic versioning, it is very difficult to evolve a module in a backwards compatible manner. Sometimes breaking changes are needed to get away from previous bad design decisions, but you still don't want to break existing clients, and wants to be able to provide bug fixes for those.
That is, allow v1.1 to be published, even if there is a v2.0.
See http://semver.org/ for details.
Thanks for the suggestion. This one may be a bit tougher than others. However, your point is clear – there’s no way to rev an older version of a module once you have published a major version due to a breaking change.