Yes, that's usually the best strategy for most of us.
But a standard library is a little different due to the sheer number of dependencies and level of coordination needed to upgrade them all. Go got it mostly right the first time, and the lack of churn is a major advantage.
So upgrades are optional and not pulling the rug out from underneath the feet of devs.
Major releases allows the project to make corrections and avoid carrying around years of baggage.