-
-
Notifications
You must be signed in to change notification settings - Fork 673
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
warning when upgrading from 0.50 -> 0.51 #4199
Comments
What's the version for |
there is no rules_go mentioned anywhere in my |
|
i am not running with in fact i just now tried adding
still getting the same warning |
No no, don't use |
Could you check whether bazel-contrib/bazel-gazelle#2003 fixes this? |
**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**
What version of rules_go are you using?
0.51.0
What version of gazelle are you using?
0.40.0
What version of Bazel are you using?
7.4.1
Does this issue reproduce with the latest releases of all the above?
yes
What operating system and processor architecture are you using?
linux
x64
Any other potentially useful information about your toolchain?
What did you do?
What did you expect to see?
no warning
What did you see instead?
The text was updated successfully, but these errors were encountered: