Update dependency io_bazel_rules_go to v0.41.0 #3417
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v0.40.1
->v0.41.0
Release Notes
bazelbuild/rules_go (io_bazel_rules_go)
v0.41.0
Compare Source
What's Changed
Starting this release, rules_go no longer ship with
@go_googleapis
repo. Together with Gazelle v0.32.0, it means that all Go code importing generated code from Google APIs will depend on@org_golang_google_genproto
, which is resolved by Go modules. For proto files importing Google APIs proto, people needs to:http_archive
rule to download Google APIs, e.g.,Other changes included in this release
go_sdk
extension failure for unnamed root module by @fmeum in https://github.com/bazelbuild/rules_go/pull/3612Full Changelog: bazel-contrib/rules_go@v0.40.1...v0.41.0
WORKSPACE
codeConfiguration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.