Bump protobuf from 34.0.bcr.1 to 35.1

[dependabot]

Bumps protobuf from 34.0.bcr.1 to 35.1.

Release notes

Sourced from protobuf's releases.

Protocol Buffers v35.1

Announcements

• Protobuf News may include additional announcements or pre-announcements for upcoming changes.

Bazel

• Bazel 9 tests for csharp, hpb, objc, php, python, rust and upb (#27598) (protocolbuffers/protobuf@4469e38)
• Break protobuf dependency on Bazel's proto fragment. Only respect the Starlark versions of --proto_toolchain_for*. This is a breaking change from 35.0, but matches the behavior in 34.x. (protocolbuffers/protobuf@1f99c52)

C++

• Add cord setters to repeated string fields. (protocolbuffers/protobuf@6efa174)

UPB (Python/PHP/Ruby C-Extension)

• Avoid UB in upb by switching to the XCT section, which will run our constructors before the compiler-generated initializers. (protocolbuffers/protobuf@c35b977)

Protocol Buffers v35.0

Announcements

• Protobuf News may include additional announcements or pre-announcements for upcoming changes.

Bazel

• Bazel 9 Support: Upgrade tests to Bazel 9 (protocolbuffers/protobuf@3ee8d8a)
• Moved protocopt flag out of the cc dir, since it is not a c++-specific flag. (protocolbuffers/protobuf@325d8dc)
• Add support for bazel 9.x (#26201) (protocolbuffers/protobuf@f08d703)
• Change @protobuf//bazel/flags:prefer_prebuilt_proto flag to True. (protocolbuffers/protobuf@f9f32d2)
• Dropped support for Bazel 7. (protocolbuffers/protobuf@1816758)

Compiler

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

C++

• Workaround for attribute handling bug in gcc < 13 (protocolbuffers/protobuf@78dc67e)
• Implement the Edition 2026 naming style enforcement feature. This will help prevent field name collisions. (protocolbuffers/protobuf@ae0d964)
• Add enum to enforce_naming_style feature to avoid field naming collisions which will be implemented in Edition 2026. (protocolbuffers/protobuf@e4911a1)
• Enhance ParseInfoTree to provide location of names and values. (protocolbuffers/protobuf@1cb4fdb)
• Add integer overflow check to RepeatedPtrField::MergeFrom. (protocolbuffers/protobuf@cb5fe97)
• Adding sanity check for ListFields reflection call (protocolbuffers/protobuf@555360e)
• Introduce Arena::UniquePtr and Arena::Ptr as smart pointers to better manage (protocolbuffers/protobuf@bb00218)
• 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. (protocolbuffers/protobuf@5a56dee)
• Fixed data race in Python Free Threading by removing unnecessary SetHasBitForRepeated() call. (protocolbuffers/protobuf@8c1a9a4)

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[mxpv]

@dependabot ignore this major version

[dependabot]

OK, I won't notify you about version 35.x.x again, unless you re-open this PR.