chore(deps): update dependency rules_proto to v7 #419
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:
5.3.0-21.7
->7.0.2
Release Notes
bazelbuild/rules_proto (rules_proto)
v7.0.2
Compare Source
Using bzlmod with Bazel 6 or later:
[Bazel 6] Add
common --enable_bzlmod
to.bazelrc
.Add to your
MODULE.bazel
file:Using WORKSPACE:
What's Changed
Full Changelog: bazelbuild/rules_proto@7.0.1...7.0.2
v7.0.1
Compare Source
Using bzlmod with Bazel 6 or later:
[Bazel 6] Add
common --enable_bzlmod
to.bazelrc
.Add to your
MODULE.bazel
file:Using WORKSPACE:
What's Changed
Full Changelog: bazelbuild/rules_proto@7.0.0...7.0.1
v7.0.0
Compare Source
Using bzlmod with Bazel 6 or later:
[Bazel 6] Add
common --enable_bzlmod
to.bazelrc
.Add to your
MODULE.bazel
file:Using WORKSPACE:
What's Changed
Full Changelog: bazelbuild/rules_proto@6.0.2...7.0.0
v6.0.2
Compare Source
Using bzlmod with Bazel 6 or later:
[Bazel 6] Add
common --enable_bzlmod
to.bazelrc
.Add to your
MODULE.bazel
file:Using WORKSPACE:
What's Changed
Full Changelog: bazelbuild/rules_proto@6.0.0...6.0.2
v6.0.0
Compare Source
NEW FEATURES
When used with Bazel 7, Protobuf Toolchainization is now available. This allows you to choose where the protobuf compiler (
protoc
) comes from, as well as configure a toolchain for each language you generate proto stubs for.This de-couples rules_proto from the https://github.com/protocolbuffers/protobuf repository;
rules_proto
no longer depends oncom_google_protobuf
. The Bazel rules in that repository are now maintained by the protobuf team for Google use cases, and may diverge from rules_proto over time.rules_proto does not include the toolchain implementation. See https://registry.bazel.build/modules/toolchains_protoc for an example module that registers the prebuilt binary from https://github.com/protocolbuffers/protobuf/releases.
The tracking issue for this feature is #179
BREAKING CHANGES
Upgrading from rules_proto 5.x requires some changes:
load
site forrules_proto_toolchains
has changed. See the new WORKSPACE snippet below.com_google_protobuf
). As a result, therules_proto_dependencies
macro no longer fetches one. For WORKSPACE users, this may affect what version of protobuf you end up with. We recommend explicitly fetchingcom_google_protobuf
early in the WORKSPACE file, as the first declaration wins.Install
Using bzlmod with Bazel 6 or later:
[Bazel 6] Add
common --enable_bzlmod
to.bazelrc
.Add to your
MODULE.bazel
file:Using WORKSPACE:
What's Changed
2f8c04c
by @shaldengeki in https://github.com/bazelbuild/rules_proto/pull/130New Contributors
Full Changelog: bazelbuild/rules_proto@4.0.0...6.0.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 was generated by Mend Renovate. View the repository job log.