Protocol Buffers

What's new in this version:

Bazel:
- Bazel 9 Support: Upgrade tests to Bazel 9
- Moved protocopt flag out of the cc dir, since it is not a c++-specific flag
- Add support for bazel 9.x
- Change @protobuf//bazel/flags:prefer_prebuilt_proto flag to True
- Dropped support for Bazel 7

Compiler:
- Implement the Edition 2026 naming style enforcement feature. This will help prevent field name collisions
- Add enum to enforce_naming_style feature to avoid field naming collisions which will be implemented in Edition 2026
- Fail writing files in protoc CLI if any file output path is relative
- Mangle types named XyzView if there is any direct sibling named Xyz
- Improve the namespacing selected by rustc used for gencode types in errors
- Fully qualify scalar types in Kotlin/Native proto generator
- Change _opt() accessors to return an std::Option instead of protobuf::Optional
- Make Message's trait bounds much better for generic use
- Support more chars in type URLs in the C++ text-format parser
- Validate Feature Support on Custom Options
- Trait clarity effort: introduce Singular trait, for types which are allowed as simple fields
- Trait clarity improvement on Map traits

C++:
- Workaround for attribute handling bug in gcc < 13
- Implement the Edition 2026 naming style enforcement feature. This will help prevent field name collisions
- Add enum to enforce_naming_style feature to avoid field naming collisions which will be implemented in Edition 2026
- Enhance ParseInfoTree to provide location of names and values
- Add integer overflow check to RepeatedPtrField::MergeFrom
- Adding sanity check for ListFields reflection call
- Introduce Arena::UniquePtr and Arena::Ptr as smart pointers to better manage
- Bug fix for edition 2024 visibility checking. Visibility checking was not properly applied to service method input and output types. This is now applied properly and will error if method input/output types do not have visibility to those messages
- Fixed data race in Python Free Threading by removing unnecessary SetHasBitForRepeated() call
- Add support for bazel 9.x
- Add proto2::sort/stable_sort utilities that behave as the standard ones but are optimized for Protobuf containers
- Add proto2::erase/erase_if utilities that behave as the standard ones but are optimized for Protobuf containers
- Extend Abseil flag support for enums to include std::vector
- Dropped support for Bazel 7
- Add native Abseil flag support to protobuf message types
- Support more chars in type URLs in the C++ text-format parser
- Stripping empty options
- Creating generic MaybeAddError helper function
- Validate Feature Support on Custom Options
- Add bounds checks to UnsafeArenaExtractSubrange, ReleaseLast and SwapElements
- Fix UTF-8 Validation of string extensions in C++
- Remove first implementation of protobuf out of bounds enforcement
- Add native Abseil flag support to protobuf enums
- Improve EINTR handling for close in zero_copy_stream_impl.h
- Add cc_proto_library for MessageSet in //src/google/protobuf/bridge

Java:
- Add BytecodeClassName functions, matching helpers in the java GeneratorNames utility
- Add enum to enforce_naming_style feature to avoid field naming collisions which will be implemented in Edition 2026
- Avoid toBigIntegerExact in JsonFormat to avoid degenerate parse behavior in the face of large exponents
- Dropped support for Bazel 7
- Add native Abseil flag support to protobuf enums

Csharp:
- Implement WriteDelimitedTo(BufferWriter)
- Add an "include" directory containing WKTs for Google.Protobuf.Tools nuget package

Objective-C:
- ObjC: Block Roots from being created
- Fix naming convention in c_function extension syntax
- Modify unit tests to use c_function extension syntax via ifdefs

Rust:
- Mangle types named XyzView if there is any direct sibling named Xyz
- Improve the namespacing selected by rustc used for gencode types in errors
- Allow ProtoStr to be used in const contexts
- Make any &T impl AsView if T impl AsView
- Change _opt() accessors to return an std::Option instead of protobuf::Optional
- Add some common methods to ProtoStr to make it more ergonomic to use without dropping down to &[u8]
- Ffi_11: Define basic arithmetic operations and comparison with underlying type
- Make Message's trait bounds much better for generic use
- Remove ProxiedInMapValue alias, since it is superceded by MapValue
- Add fn push_default(&mut self) -> SomeMsgMut<> fn for Repeated message type fields
- Fix that f32 and f64 were incorrectly tagged as legal for MapKeys in RustProto
- Trait clarity effort: introduce Singular trait, for types which are allowed as simple fields
- Trait clarity improvement on Map traits
- See also UPB changes below, which may affect Rust

Python:
- Fix Python text_format by adding an optional recursion depth limit
- Fix data race in CMessage lazy initialization for Python freethreading
- Fixed data race in Python Free Threading by removing unnecessary SetHasBitForRepeated() call
- Fix type annotation for FindAllExtensionNumbers() to be a list rather than the more general Iterator
- Add type hints to descriptor_database.py
- Fixed a bug in msg.MergeFrom(msg2) in Python
- Fix NULL byte handling issue in Python Protobuf find symbols in pool
- Add support for bazel 9.x
- Add recursion guards for the following nested messages:
- Protobuf Python UPB Free Threading support
- Fix Any recursion depth bypass in Python json_format.ParseDict
- Supports exporting int as int

PHP:
- Fail writing files in protoc CLI if any file output path is relative

PHP C-Extension:
- Fix 1-byte stack overflow in PHP extension int64 formatting
- See also UPB changes below, which may affect PHP C-Extension

Ruby:
- Gracefully handle payloads >2GB

Ruby C-Extension:
- Gracefully handle payloads >2GB
- See also UPB changes below, which may affect Ruby C-Extension

UPB (Python/PHP/Ruby C-Extension):
- Fixed two GCC-only issues around upb's generated extension registry
- Avoid theoretical overflow of uintptr_t in AddAllLinkedExtensions
- Test(proto): Add message to test oneof name conflict resolution
- Add recursion guards for the following nested messages