Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix go_deps warnings #2003

Merged
merged 1 commit into from
Jan 6, 2025
Merged

Fix go_deps warnings #2003

merged 1 commit into from
Jan 6, 2025

Conversation

fmeum
Copy link
Member

@fmeum fmeum commented Jan 4, 2025

What type of PR is this?

Bug fix

What package or component does this PR mostly affect?

go_deps

What does this PR do? Why is it needed?

  • Only show a warning for version mismatches between go.mod and bazel_dep if the dep is either a direct dep or the Bazel module version is lower. This avoids noisy warnings, in particular on gazelle itself due to its go.mod dependency on rules_go.
  • Don't suggest importing deps from isolated usages that are shared with the non-isolated usage.

Which issues(s) does this PR fix?

Fixes bazel-contrib/rules_go#4199
Work towards #1990

Other notes for review

* Only show a warning for version mismatches between `go.mod` and `bazel_dep` if the dep is either a direct dep or the Bazel module version is lower. This avoids noisy warnings, in particular on gazelle itself due to its `go.mod` dependency on `rules_go`.
* Don't suggest importing deps from isolated usages that are shared with the non-isolated usage.
@fmeum fmeum merged commit 661b2a0 into master Jan 6, 2025
16 checks passed
@fmeum fmeum deleted the rules_go-4199-drop-dep branch January 6, 2025 08:01
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.

warning when upgrading from 0.50 -> 0.51
2 participants