-
Notifications
You must be signed in to change notification settings - Fork 691
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
Upgrade rules_go and Gazelle #2035
Conversation
|
||
# TODO: `go_repository_default_config` is only useful for working around | ||
# https://github.com/bazelbuild/rules_docker/issues/1902 and could likely be | ||
# removed after https://github.com/bazelbuild/rules_docker/issues/1787 | ||
def go_deps(go_repository_default_config = "@//:WORKSPACE"): | ||
def go_deps(): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this looks like a breaking change for users?
FWIW: I'm currently using this on an M1 Mac to successfully cross-compile linux_amd64 containers using Bazel 4.2.2 |
This Pull Request has been automatically marked as stale because it has not had any activity for 180 days. It will be closed if no further activity occurs in 30 days. |
This PR was automatically closed because it went 30 days without a reply since it was labeled "Can Close?" |
Why is this PR close? people using M1 host seem to have issues with it. |
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
rules_go and Gazelle are pretty old
Issue Number: #2036
What is the new behavior?
Does this PR introduce a breaking change?
Other information
New rules_go no longer allows to call
go_register_toolchains
multiple times, so we have to move it out ofgo_deps
, because it will be called another time inpython/image.bzl
.