Yeeeah, this made me lose half a day learning about and then unwinding “toolchain” being accidentally set across all our microservices…

Made a little harder to track down initially as we have a replace directive pointing to a local proto module in each service. It was here that toolchain was set which forced it to keep appearing in the top level module.

Should’ve been opt in behaviour by default not enforced.

We’ve decided to sit on n-1 of Go and I’ve already had an example last month of a well used OSS library setting toolchain to 1.22 as a patch release (which could be considered a breaking change) which fortunately was quickly reverted.