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

Upgrade rules_go and Gazelle #2035

Closed
wants to merge 2 commits into from
Closed

Conversation

linzhp
Copy link
Collaborator

@linzhp linzhp commented Mar 1, 2022

PR Checklist

Please check if your PR fulfills the following requirements:

  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • Other... Please describe:

What is the current behavior?

rules_go and Gazelle are pretty old

Issue Number: #2036

What is the new behavior?

  • Upgrade rules_go to 0.30
  • Upgrade Gazelle to 0.24
  • Upgrade Bazel to 5.0, because rules_go requires Bazel 4.2.1

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

New rules_go no longer allows to call go_register_toolchains multiple times, so we have to move it out of go_deps, because it will be called another time in python/image.bzl.

@linzhp linzhp marked this pull request as draft March 1, 2022 16:10

# 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():
Copy link
Collaborator

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?

@linzhp linzhp mentioned this pull request May 5, 2022
10 tasks
@ricochet1k
Copy link

FWIW: I'm currently using this on an M1 Mac to successfully cross-compile linux_amd64 containers using Bazel 4.2.2

@github-actions
Copy link

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.
Collaborators can add an assignee to keep this open indefinitely. Thanks for your contributions to rules_docker!

@github-actions github-actions bot added the Can Close? Will close in 30 days unless there is a comment indicating why not label Dec 26, 2022
@github-actions
Copy link

This PR was automatically closed because it went 30 days without a reply since it was labeled "Can Close?"

@github-actions github-actions bot closed this Jan 25, 2023
@thesayyn
Copy link

Why is this PR close? people using M1 host seem to have issues with it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Can Close? Will close in 30 days unless there is a comment indicating why not
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants