Skip to content

Conversation

@fmeum
Copy link
Contributor

@fmeum fmeum commented Jan 7, 2025

When bazelisk is brought in as a Go dependency via gazelle's go_deps extension, it uses the repo mapping of the gazelle module to resolve loads. Since gazelle uses the legacy apparent names bazel_gazelle and io_bazel_rules_go for the gazelle and rules_go modules, the same is required for any Bazel module that is also a Go module (until gazelle gains the ability to fix load labels).

This regressed in 4448ad1.

@fmeum
Copy link
Contributor Author

fmeum commented Jan 7, 2025

@fweikert @meteorcloudy

@meteorcloudy meteorcloudy merged commit 0a4dc6b into bazelbuild:master Jan 7, 2025
2 checks passed
@fmeum fmeum deleted the fix-gazelle-usage branch January 7, 2025 10:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants