This version includes breaking changes to C++, Objective-C, Python, Rust:


   - 
   
   [C++] Remove deprecated APIs. 
   - 
   
   [C++] Remove CMake submodule support in favor of fetched or installed 
   dependencies. 
   - 
   
   [C++] Prohibit using Bazel+MSVC to build protobuf 
   - 
   
   [C++] Strip ctype from options in C++ 
   - 
   
   [C++] Remove MutableRepeatedFieldRef::Reserve() in reflection
   - 
   
   [C++] Upgrade return type of several string returning functions to 
   absl::string_view. 
   - 
   
   [C++] Flip default behavior for handling cmake dependencies. 
   - 
   
   [C++] Add ASAN poisoning after clearing oneof messages on arena. 
   - 
   
   [Objective-C] Remove legacy WKT headers.
   - 
   
   [Objective-C] Upgrade return type of several string returning functions 
   to absl::string_view. 
   - 
   
   [Python] Remove deprecated APIs
   - 
   
   [Python] Upgrade return type of several string returning functions to 
   absl::string_view. 
   - 
   
   [Python] Fix closed enum validation under editions 
   - 
   
   [Python] Python setdefault behavior change for map field.
   - 
   
   [Python] Python nested message class qualname now contains the outer 
   message name. 
   

View changes since 30.0-RC1 here 
<https://github.com/protocolbuffers/protobuf/compare/main...30.x>.

You can view the release and complete release notes on GitHub 
<https://github.com/protocolbuffers/protobuf/releases/tag/v30.0-rc1> and 
additional information on our News page <https://protobuf.dev/news/>.

If you experience any issues with the release, please file a bug 
<https://github.com/protocolbuffers/protobuf/issues/new/choose> or post on the 
Protocol Buffers forum <https://groups.google.com/g/protobuf>.

-- 
You received this message because you are subscribed to the Google Groups 
"Protocol Buffers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/d/msgid/protobuf/072842b9-1124-40e3-a638-40a3da395b64n%40googlegroups.com.

Reply via email to