Repository navigation
chore(deps): update dependency protobuf to v36 - #2476
cgrindel-self-hosted-renovate[bot] wants to merge 1 commit into
Conversation
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
|
@Mergifyio queue |
Merge Queue Status
Waiting for
All conditions
|
|
Blocked on an upstream bug: protobuf 36.0 ships the wrong protoc checksums for macOS. The only real failure is Claude checked this against the actual release artifacts.
The release assets were never re-uploaded after publication (every Nothing in this repo can work around it. It needs a protobuf 36.0.x release or a BCR Holding this PR until then. Note that BCR also has protobuf 35.1, which is an unblocked intermediate step off 35.0 if we want one. |
9803659 to
25bc1ac
Compare
25bc1ac to
0401305
Compare
This PR contains the following updates:
35.1→36.2Release Notes
protocolbuffers/protobuf (protobuf)
v36.2: Protocol Buffers v36.2Announcements
Compiler
3078015)7390c85)7ed8a4b)Csharp
57ef94f)Rust
8b6311f)10b8b5e)3078015)7390c85)7ed8a4b)7aca0ec)2198c6b)UPB (Python/PHP/Ruby C-Extension)
upb/port/BUILD(7ff0f88)v36.1: Protocol Buffers v36.1Announcements
Csharp
cc7e6bd)Rust
e64a176)fecb404)1312f3b)fbf3069)Python
333846a)210324c)v36.0: Protocol Buffers v36.0Announcements
Bazel
90ad7e9)f9e028f)Compiler
fcd68c5)517be42)933c522)81880fa)--<lang>_prefixcli option (#24824) (92dd27c)d8520d9)28bef98)enforce_proto_limitsfeature which will be implemented in Edition 2026. (5ddd524)C++
1d8a656)json_options.protoandjson_enumvalue_options.protoand/or gencode derived from them to release artifacts (15e9334)Reflection::GetEnum()andReflection::GetRepeatedEnum(). (0bca288)271ca53)e337495)fcd68c5)e75aac3)81880fa)2718dd5)d8520d9)enforce_proto_limitsfeature which will be implemented in Edition 2026. (5ddd524)ba10a4e)7864b85)0bc1f14)Java
With this release JavaProto no longer uses
sun.misc.Unsafeas long as you are utilizing the standard generated code. You should no longer see warnings printed aboutsun.misc.Unsafe. If you see any issues, please let us know on #20760Note that the runtime itself still contains references to sun.misc.Unsafe in paths which are exclusively to support Lite generated code. Lite is emitted by a separate code generator which creates generated code optimized for mobile clientside contexts, especially alongside R8 optimizations. Android does not have a timeline to removing
sun.misc.Unsafe, and we have found the performance regression too significant to consider removing these paths at this time. It is still TBD for how we can best navigate this mobile vs JVM split on this topic.json_options.protoandjson_enumvalue_options.protoand/or gencode derived from them to release artifacts (15e9334)bff6ed1)d5e039a)ab69831)fcd68c5)c56cd5b)517be42)31ef11c)ae1faee)40825a1)81880fa)ec52338)a37dbd6)421d745)String#encodedLengthon JDK versions that support it (efca121)enforce_proto_limitsfeature which will be implemented in Edition 2026. (5ddd524)25e7005)f8514d8)Csharp
156d42d)f11aac4)34e959b)fcd68c5)a1f718c)7a732d1)81880fa)cee45bf)csharpstring interpolation inTimestamp.ToDateTime()exception message (#26341) (a298282)Objective-C
f89baed)81880fa)290a537)Rust
96e772f)e7b3391)81880fa)70590a5)Python
json_options.protoandjson_enumvalue_options.protoand/or gencode derived from them to release artifacts (15e9334)2255541)5865e6b)271ca53)3aa022a)9e9dbae)abdf212)3d31b0f)a70d121)ea40f1d)map<string, ...>key handling forbyteslookups. (156a0b8)e86e536)593ab17)e090f8a)403d429)81880fa)cecbbf4)c857f49)cfcc433)78a09ad)PHP
49b3b18)e171c67)34e959b)eff2323)47c8651)5c5ee3c)81880fa)0488596)enforce_proto_limitsfeature which will be implemented in Edition 2026. (5ddd524)PHP C-Extension
49b3b18)47c8651)5c5ee3c)Ruby
34e959b)7008dd1)81880fa)UPB (Python/PHP/Ruby C-Extension)
0e8519e)58e5ac8)403d429)0488596)90ad7e9)d56b385)78a09ad)Other
daf4964)c4846de)2d3c0d3)a8d0be3)Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate CLI.