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.

Sign up for GitHub

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

Jump to bottom

sluongng/upgrade rules go #3699

Closed
wants to merge 4 commits into from
Closed

sluongng/upgrade rules go #3699

wants to merge 4 commits into from

Commits on Apr 1, 2023

  1. Upgrade rules_go and gazelle to latest version 

    - Upgraded rules_go to v0.39.0
- Upgraded gazelle to v0.30.0
  + Patch visibility of @gazelle//internal/module to build `bb` CLI
- Upgraded go to 1.20.2
- Upgrade several golang.org/x/... packages

This also required us to change how we are registering go_sdk. An issue
was reported upstream here bazelbuild/rules_go#3510
    @sluongng
    sluongng committed Apr 1, 2023
    Configuration menu
    Copy the full SHA
    0f94b1e View commit details
    Browse the repository at this point in the history

  2. Upgrade gazelle go deps

    @sluongng
    sluongng committed Apr 1, 2023
    Configuration menu
    Copy the full SHA
    e661893 View commit details
    Browse the repository at this point in the history

  3. Run new gazelle over repo 

    Fix all the visibility scope issues that was reported in
bazelbuild/bazel-gazelle#1467
    @sluongng
    sluongng committed Apr 1, 2023
    Configuration menu
    Copy the full SHA
    f378b4b View commit details
    Browse the repository at this point in the history

Commits on Apr 10, 2023

  1. Patch rules_go with bazelbuild/rules_go#3511

    @sluongng
    sluongng committed Apr 10, 2023
    Configuration menu
    Copy the full SHA
    2b30e6f View commit details
    Browse the repository at this point in the history