-
-
Notifications
You must be signed in to change notification settings - Fork 662
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
nogo_main fail to build when to upgrade golang.org/x/tools #3640
Comments
@sluongng Do you happen to have a recommendation here? Should we just update the version used by rules_go and force users to update with us? |
I think we also ran into a separate issue with
Yeah, there is no way we could accommodate a matrix of 3rd party deps version ranges. I think we need to bump x/tools version in both rules_go and gazelle to the latest and do new releases. |
This PR prepares a new minor release 0.33.0 which includes no large breaking changes, yet some enhancements to Bzlmod ecosystem, including a new archive_override tag for the go_deps extension. This PR does not include an update to the x/tools dependency because it is not included in the go.mod file, and there is a known bug: bazel-contrib/rules_go#3640 This PR also adds a missing license header to files in the repository.
This PR prepares a new minor release 0.33.0 which includes no large breaking changes, yet some enhancements to Bzlmod ecosystem, including a new archive_override tag for the go_deps extension. This PR does not include an update to the x/tools dependency because it is not included in the go.mod file, and there is a known bug: bazel-contrib/rules_go#3640 This PR also adds a missing license header to files in the repository.
What version of rules_go are you using?
What version of gazelle are you using?
What version of Bazel are you using?
Build label: 6.3.1-homebrew
Does this issue reproduce with the latest releases of all the above?
if you update the tools like this
you will get the error
What operating system and processor architecture are you using?
Any other potentially useful information about your toolchain?
What did you do?
What did you expect to see?
What did you see instead?
The text was updated successfully, but these errors were encountered: