It's funny. With Go modules, though, there's a very real consequence of moving to 1.0.x; the build system starts imposing different constraints. Same with the move to 2.0.x. Changing versions means more than just throwing a tag in the VCS.
Most of the time, it's what you'd do anyway and isn't a bother. Sometimes - not often, but non-zero - it's an imposition.
It's funny. With Go modules, though, there's a very real consequence of moving to 1.0.x; the build system starts imposing different constraints. Same with the move to 2.0.x. Changing versions means more than just throwing a tag in the VCS.
Most of the time, it's what you'd do anyway and isn't a bother. Sometimes - not often, but non-zero - it's an imposition.