Build text-2.13.0 did NOT complete successfully

Building tensorflow-text encounted the errors on Mac M1 for Python 3.11

external/com_google_protobuf/src/google/protobuf/compiler/cpp/enum_field.h:51:25: error: only virtual member functions can be marked 'override'
  ~EnumFieldGenerator() override;
                        ^
external/com_google_protobuf/src/google/protobuf/compiler/cpp/enum_field.h:54:59: error: only virtual member functions can be marked 'override'
  void GeneratePrivateMembers(io::Printer* printer) const override;
                                                          ^
..........

fatal error: too many errors emitted, stopping now [-ferror-limit=]
1 warning and 20 errors generated.
Target //oss_scripts/pip_package:build_pip_package failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 4.042s, Critical Path: 1.43s
INFO: 55 processes: 20 internal, 35 local.
FAILED: Build did NOT complete successfully

All printed errors were about this override.

One thing I noticed was that tensorflow already changed bazel version to 6.1.0. However, the file during text build still downloaded .bazeversion file referring to 5.3.0.

Could this be a reason for the failure?

Start by comparing the repository's Bazel configuration with the .bazelversion file used during the text build, especially the reported 5.3.0 versus TensorFlow's 6.1.0. Reproduce the Mac M1 Python 3.11 failure through //oss_scripts/pip_package:build_pip_package with verbose failures, then determine whether the protobuf override errors disappear with the expected build configuration.