chore(deps): update dependency io_bazel_rules_go to v0.41.0 - autoclosed #104
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.37.0
->v0.41.0
Release Notes
bazelbuild/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 and generating Go code, users need to:http_archive
rule to download Google APIs, e.g.,Note that the version of Google APIs archive needs to be compatible with the pre-generated code in
@org_golang_google_genproto
.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: bazelbuild/rules_go@v0.40.1...v0.41.0
WORKSPACE
codev0.40.1
Compare Source
WORKSPACE
codeChanges
This patch release cherry-picked two bug fixes related to Go package driver from master
v0.40.0
Compare Source
What's Changed
goexperiment.*
build tags by @lbcjbb in https://github.com/bazelbuild/rules_go/pull/3556go_path
'slink
mode by @fmeum in https://github.com/bazelbuild/rules_go/pull/3565--incompatible_disable_starlark_host_transitions
by @fmeum in https://github.com/bazelbuild/rules_go/pull/3560.go
file in a random location by @fmeum in https://github.com/bazelbuild/rules_go/pull/3566use_repo
automation by @fmeum in https://github.com/bazelbuild/rules_go/pull/3573go_host_compatible_sdk
repository by @ylecornec in https://github.com/bazelbuild/rules_go/pull/3543gazelle:prefix
can be replaced bygo.mod
by @fmeum in https://github.com/bazelbuild/rules_go/pull/3577go_download_sdk
with Bazel dev versions by @fmeum in https://github.com/bazelbuild/rules_go/pull/3580New Contributors
Full Changelog: bazelbuild/rules_go@v0.39.1...v0.40.0
WORKSPACE
codev0.39.1
Compare Source
What's Changed
Full Changelog: bazelbuild/rules_go@v0.39.0...v0.39.1
v0.39.0
Compare Source
WORKSPACE
codeWhat's Changed
go
binary available as a target by @fmeum in https://github.com/bazelbuild/rules_go/pull/3429filter_transition_label
workaround by @fmeum in https://github.com/bazelbuild/rules_go/pull/3438x_defs
values by @fmeum in https://github.com/bazelbuild/rules_go/pull/3473//go
usable in scripts run withbazel run
by @fmeum in https://github.com/bazelbuild/rules_go/pull/3474error
script ingo_cross_binary
by @fmeum in https://github.com/bazelbuild/rules_go/pull/3481CC
if it contains whitespace by @fmeum in https://github.com/bazelbuild/rules_go/pull/3491runtime/cgo
withpure = False
by @fmeum in https://github.com/bazelbuild/rules_go/pull/3492ctx.readdir
instead ofls
for SDK platform detection by @fmeum in https://github.com/bazelbuild/rules_go/pull/3497New Contributors
Full Changelog: bazelbuild/rules_go@v0.38.0...v0.39.0
v0.38.1
Compare Source
Bug fixes
The go_googleapis upgrade in 0.38.0 is too disruptive. It changes the Go import paths of the proto packages, causing build failures in repos trying to upgrade to rules_go 0.38.0. Reverting the go_googleapis to the master of 2022-12-05 (#3432) for now to make rules_go upgrades easier.
WORKSPACE
codeFull Changelog: bazelbuild/rules_go@v0.38.0...v0.38.1
v0.38.0
Compare Source
Breaking changes
Starting this release, rules_go requires Bazel 5.3 and golang/x/tools at least 0.3.0. If you are using stardoc, you also need to upgrade it to 0.5.3 to recognize
RunEnvironmentInfo
, which is used in this release.Major new features
This is the first release to support Go 1.20. When on this version of Go, it is highly recommended to use Bazel 6 and set
--experimental_output_directory_naming_scheme=diff_against_baseline
to prevent certain unnecessary rebuilds.What's Changed
-work
is specified by @motiejus in https://github.com/bazelbuild/rules_go/pull/3389lcov_coverage_test
toexec.Command
change by @fmeum in https://github.com/bazelbuild/rules_go/pull/3392boringcrypto
toGOEXPERIMENT
support by @fmeum in https://github.com/bazelbuild/rules_go/pull/3401cfg = "host"
withcfg = "exec"
by @fmeum in https://github.com/bazelbuild/rules_go/pull/3404nogo
targets asmanual
to keep top-level symlinks by @fmeum in https://github.com/bazelbuild/rules_go/pull/3410env
attribute togo_binary
by @fmeum in https://github.com/bazelbuild/rules_go/pull/3428New Contributors
Full Changelog: bazelbuild/rules_go@v0.37.0...v0.38.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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.