protobuf 26.1

[chenrui333]

Created by brew bump

---

Created with brew bump-formula-pr.

[scpeters]

I saw the following comment in #166096

Using Python bindings with C++ backend is deprecated and we are removing them from formula in #166008. Officially need to use PyPI source to build with UPB backend (or Bazel in git source but usually better to avoid Bazel).

Is this a change for protobuf only, or is this a policy change for all homebrew formulae (deprecation of python bindings with c++ backend)? If it's a broader change and there's a tracking issue, apologies that I've missed it, and I would appreciate if you could share a link to it.

If this is only for protobuf, then carry on!

[chenrui333]

@scpeters only for protobuf at the moment

[cho-m]

Is this a change for protobuf only, or is this a policy change for all homebrew formulae (deprecation of python bindings with c++ backend)?

only for protobuf at the moment

Specifically, we are following upstream instructions. If upstream supports Python bindings with C++ backend, we will keep them.

Protobuf doesn't want users/downstreams to build this anymore - protocolbuffers/protobuf@5722aef

[scpeters]

Is this a change for protobuf only, or is this a policy change for all homebrew formulae (deprecation of python bindings with c++ backend)?

only for protobuf at the moment

Specifically, we are following upstream instructions. If upstream supports Python bindings with C++ backend, we will keep them.

Protobuf doesn't want users/downstreams to build this anymore - protocolbuffers/protobuf@5722aef

thanks for the info!

[scpeters]

glancing at the grpc failure, it looks like it is caused by an API change in protobuf and needs grpc/grpc#35898

[cho-m]

Need to figure out how to deal with or-tools. It is only compatible with Protobuf 25. I did try building bundled copy but that links conflicting libs into HOMEBREW_PREFIX. Given that it is only a single formula, I may just resource Protobuf 25 into libexec but will need to figure out how to fix up CMake files to pick correct copy.

Other failures are:

• bear - rizsotto/Bear@4d9d452
• mavsdk - need to regenerate files with newer protoc
• nanopb - will need a virtualenv for protobuf python libs
• sysdig - revision bump

EDIT: There is also a new minor version but I'm not sure if that will invalidate our bottle cache. So may just want to stick to current protobuf version