bazel build //... fails with bazel 7.1.1

[proppy]

bazel_rules_hdl 👺  bazel --version
bazel 7.1.1
bazel_rules_hdl 🍡  bazel build //...
INFO: Invocation ID: f84bb39a-10fb-4d90-8092-446af9e676f9
Computing main repo mapping: 
Computing main repo mapping: 
Loading: 
Loading: 0 packages loaded
bazel: Entering directory `/home/proppy/.cache/bazel/_bazel_proppy/530ec4e06f73c694e11ff02f6133cd51/execroot/_main/'
Analyzing: 898 targets (75 packages loaded, 0 targets configured)
Analyzing: 898 targets (75 packages loaded, 0 targets configured)
[0 / 1] [Prepa] BazelWorkspaceStatusAction stable-status.txt
Analyzing: 898 targets (145 packages loaded, 642 targets configured)
[9 / 9] checking cached actions
Analyzing: 898 targets (182 packages loaded, 5999 targets configured)
[74 / 270] [Prepa] Executing genrule @@zlib~//:copy_public_headers
ERROR: /home/proppy/.cache/bazel/_bazel_proppy/530ec4e06f73c694e11ff02f6133cd51/external/com_google_protobuf/python/BUILD.bazel:123:13: @@com_google_protobuf//python:aarch64_test_genrule: no such attribute 'exec_tools' in 'genrule' rule (did you mean 'executable'?)
ERROR: /home/proppy/.cache/bazel/_bazel_proppy/530ec4e06f73c694e11ff02f6133cd51/external/com_google_protobuf/python/BUILD.bazel:131:12: @@com_google_protobuf//python:x86_64_test_genrule: no such attribute 'exec_tools' in 'genrule' rule (did you mean 'executable'?)
ERROR: /home/proppy/.cache/bazel/_bazel_proppy/530ec4e06f73c694e11ff02f6133cd51/external/com_google_protobuf/python/BUILD.bazel:17:11: errors encountered resolving select() keys for @@com_google_protobuf//python:protobuf_python
ERROR: Loading failed
bazel: Leaving directory `/home/proppy/.cache/bazel/_bazel_proppy/530ec4e06f73c694e11ff02f6133cd51/execroot/_main/'
ERROR: Analysis of target '//pdk/proto:pdk_info_py_proto' failed; build aborted
INFO: Elapsed time: 5.482s, Critical Path: 0.53s
INFO: 101 processes: 101 internal.
ERROR: Build did NOT complete successfully
FAILED: 

[tcal-x]

+1

[QuantamHD]

We'll take a look.

[tcal-x]

We'll take a look.

It's not urgent! I can easily work around it by using bazelisk and creating a .bazelversion file containing 7.0.2 or 6.5.0 or whatever.

[tjgq]

I believe all you need to do is replace exec_tools with tools (see bazelbuild/bazel#19132).