[protobuf] [Announcement] Protocol Buffers Version 27.0-rc2 is Released!

2024-05-08 Thread 'habe...@google.com' via Protocol Buffers
You can view the release and complete release notes on GitHub . If you experience any issues with the release, please file a bug or post on the ProtocolBuffers

[protobuf] Protocol Buffers Version 26.0-rc3 is Released!

2024-02-29 Thread 'habe...@google.com' via Protocol Buffers
This version includes breaking change(s) to Ruby: - [Ruby] Moved ObjectCache into an internal module. (9087337 ) You can view the release and complete release notes on GitHub

[protobuf] Re: hasOptionalKeyword in FieldDescriptor not working in PHP

2023-05-23 Thread 'habe...@google.com' via Protocol Buffers
It looks like the PHP APIs are incomplete. It is definitely a bug that `hasOptionalKeyword()` would return this error. That said, we are guiding users away from `hasOptionalKeyword()`. Note that it is deprecated in C++:

[protobuf] Protocol Buffers Version 23.1 is Released!

2023-05-17 Thread 'habe...@google.com' via Protocol Buffers
This version includes the following non-breaking changes: *C++* - Add a workaround for GCC constexpr bug (67ecdde ) *Csharp* - [C#] Replace regex that validates descriptor names (#12174

[protobuf] Re: Generating code via protoc plugin without resolving indirect imports

2023-04-19 Thread 'habe...@google.com' via Protocol Buffers
It is strongly recommended that proto rules use aspects going forward, because it avoids the need to specify the dependency graph N times (one per language). proto_library() can specify the dependency graph once, and then any number of languages can have lang_proto_library() rules that reuse

[protobuf] Re: Generating code via protoc plugin without resolving indirect imports

2023-04-19 Thread 'habe...@google.com' via Protocol Buffers
Hi Brandon, The proto compiler doesn't generally allow what you are asking for. It always wants to see the full closure of .proto files. But if you are writing for Bazel, you shouldn't have to worry about any of that. As long as you are on Bazel >=5.3, you can use proto_common to handle most

[protobuf] Request for feedback on the Automake build

2022-03-22 Thread 'habe...@google.com' via Protocol Buffers
We are considering removing the Automake build, leaving only CMake and Bazel as supported build systems for protobuf. If anyone has use cases that depend on Automake, that cannot easily be migrated to CMake, please respond with a brief description of your use case and why CMake is not a

[protobuf] Sunsetting Python 2.7 support

2021-08-26 Thread 'habe...@google.com' via Protocol Buffers
Protobuf 3.17.3 will be the last version of protobuf to support Python 2.7. A note about this has been added to the release notes for 3.17.3 . Starting with 3.18, protobuf will require Python >= 3.5. Users who are still on