Fabian Meumertzheim

These errors are extremely weird. What is `bazel` on your system? Could you also try to run the Gazelle tests with `--spawn_strategy=local`?

Fixing this may be as easy as running the code in this `else` block unconditionally: https://github.com/bazel-contrib/bazel-gazelle/blob/227f6ac789d494e48634e848518dfaa79c22df22/internal/bzlmod/go_deps.bzl#L446 Could you give that a try?

@bstoll Assuming that both parent and child repo are checked out as sibling directories, I can get both projects to build by making the following changes: 1. Add to child's...

@oakad Could you describe your use case in more detail? If your individual projects are all Bazel projects, the approach used in https://github.com/bazel-contrib/bazel-gazelle/issues/2022#issuecomment-2886599744 should work without any manual `use_repo` meddling....

@oakad Thanks for sharing the reproducer. I think that it should just work if you add `repo_name = "io_bazel_rules_go"` to the `bazel_dep` on `rules_go` in the dep module. That's not...

I think that we could make this work without such a change, but I would still prefer making it. Go projects with releases that don't match the major version as...

The implementation looks reasonable, I'm just not sure whether this is the right way to export this information and thus don't want to commit to it yet. Could you perhaps...

@keith done

@GarilDox With Bzlmod, `update-repos` is no longer needed: https://github.com/bazelbuild/rules_go/blob/master/docs/go/core/bzlmod.md#external-dependencies. Since WORKSPACE will be disabled by default in Bazel 8, I would recommend migrating instead.

@jayconrod Could you lend your expertise here?