bin/go: No such file or directory

bazel: 8.4.2
rules_go: 0.59.0
gazelle: 0.47.0

Using go_sdk.from_file where our go.mod had 1.25.4 and now has 1.25.5 (going between commits in either direction) first run will fail and second will pass. Failures we’re seeing are like the following:

(00:41:42) ERROR: no such package '@@gazelle++go_deps+com_github_aws_aws_sdk_go_v2_service_rds//types': no such package '@@gazelle++non_module_deps+bazel_gazelle_go_repository_tools//': list_repository_tools_srcs: env: ‘/var/lib/buildkite-agent/builds/repo/bazel/bazel/bazel-user-root/output/external/rules_go++go_sdk+main___download_0/bin/go’: No such file or directory

Any one seen this and have tips for resolving it? Currently we've been just advising devs to rebase/merge main and then repush to CI. Quite painful though if they don't.

Start by reproducing the failure while switching between commits that change go.mod from Go 1.25.4 to 1.25.5. Inspect the go_sdk.from_file integration and the generated SDK path involved in the reported bin/go error. Done means the first build after switching versions succeeds without requiring a rebase or merge.

Written by the indexing model from the issue text.