I think we should just push for more date based versioning, for instance, CalVer[0]
[0]: https://calver.org/
If you don't need automatic updates, then any kind of versioning is fine. Hell, you could get away with just using a single incrementing integer. v1, v2, v3, ..., v225883, etc.
The only thing loose dependencies and automatic version resolution and duplicating libraries achieve is a false sense of security when upgrading code. And the only thing Go's awful, awful idea to force v2+ to change import path is to make a mess in your version control history, and hide the important bits in a sea of needlessly changed files.
> this whole idea of automatically updating dependencies is awful.
Yeah, well, that's just, like, your opinion, man.