update-go-version

To update the Go version across a Tempo codebase, propagate the detected version to go.mod, tools/go.mod, Dockerfiles, and CI workflows to ensure all modules and tooling remain in sync and prevent build issues.

When upgrading Go in Tempo, you must modify go.mod, tools/go.mod, tools/Dockerfile, build/tools.mk, and related CI workflow files to maintain uniform compilation and build tooling compatibility.

Cross-file Go version synchronization reads the target version from tools/Dockerfile, updates the go.mod directives, updates the TOOLS_IMAGE_TAG in build/tools.mk, and validates the compilation using make vendor and make build.

Tempo builds fail after a Go version upgrade when files like go.mod, tools/go.mod, or CI workflows are not synchronized to the same X.Y.Z version, causing dependency mismatches and tooling incompatibilities.

Yes, you can use this to sync Go versions by updating both the main and tools modules, ensuring the Dockerfile, CI workflows, and tools image tag all reflect the same Go version to maintain consistency.

Yes, you need to run make vendor and make build after updating the Go version in go.mod to validate compilation and ensure the new version does not introduce any build or dependency errors.