update_go_version

To update the Go version across a repository, you must synchronize every go.mod file, Dockerfile, and Nix configuration by applying the exact new version string to prevent module drift and build failures.

Builds fail after a Go upgrade because of subtle version drift across modules and tooling. Updating only some files leaves Dockerfiles and Nix tooling referencing the old version, causing mismatches and broken builds.

The best way to regenerate Nix hashes when changing the Go version is to run `nix store prefetch-file` to update the derived hash, ensuring the Nix tooling matches the newly specified Go release.

Yes, you need to run `make go-mod-tidy` after updating the Go version in go.mod files to ensure module dependencies are correctly resolved and synchronized with the new toolchain version.

Yes, you can update the Go version using Docker and Nix together by adjusting the Dockerfile toolchain, updating the Nix configuration, regenerating the Nix hash, and validating the Dockerfile rebuild end to end.

Manually updating Go module versions without syncing tooling leads to subtle drift where some modules lag behind, causing inconsistent builds and runtime failures across different project areas like custombuild and e2e modules.