Update dependency com.google.protobuf:protobuf-java to v3.16.3 #148
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
3.8.0
->3.16.3
By merging this PR, the below issues will be automatically resolved and closed:
Release Notes
protocolbuffers/protobuf (com.google.protobuf:protobuf-java)
v3.16.3
: Protobuf Release v3.16.3Compare Source
Java
migrate parsing logic from parse constructor to builder.
constructor" to the Builder class.
messages rather than building up a new immutable object before merging. This
way results in fewer allocations and copy operations.
instances and merging afterwards. This has much better performance.
sub-messages directly from text rather than building a new sub-message and
merging the fully formed message into the existing field.
v3.16.1
: Protocol Buffers v3.16.1Compare Source
Java
v3.16.0
: Protocol Buffers v3.16.0Compare Source
C++
calls instead of crashing.
string
orbytes
fields.RepeatedPtrField.
middle.
performance.
on an error path.
Subclasses should inherit from SimpleFieldComparator instead.
C#
Java
included as causes.
JavaScript
Python
one instead of merging.
Objective-C
PHP
Ruby
Other
v3.15.8
: Protocol Buffers v3.15.8Compare Source
Ruby
v3.15.7
: Protocol Buffers v3.15.7Compare Source
C++
Ruby
v3.15.6
: Protocol Buffers v3.15.6Compare Source
Ruby
v3.15.5
: Protocol Buffers v3.15.5Compare Source
Ruby
PHP
C++
v3.15.4
: Protocol Buffers v3.15.4Compare Source
Ruby
C++
PHP
v3.15.3
: Protocol Buffers v3.15.3Compare Source
Ruby
v3.15.2
: Protocol Buffers v3.15.2Compare Source
Ruby
C++
v3.15.1
: Protocol Buffers v3.15.1Compare Source
Ruby
C++
v3.15.0
: Protocol Buffers v3.15.0Compare Source
Protocol Compiler
the --experimental_allow_proto3_optional flag.
C++
unknown fields
implementation detail users must not rely on. It should not be used in
unit tests.
C++.
output (does not affect comparison logic) and stop printing 'value' in the
path. The modified print functionality is in the
MessageDifferencer::StreamReporter.
crash.
cases out of line.
Python
collection directly instead of using the other methods of the BaseContainer.
JavaScript
getDescriptor
methods with*
as theirthis
type.let/const
for generated messages.PHP
Ruby
upb library. This should lead to much better parsing performance,
particularly for large messages. (#8184).
recursion/run out of memory (#8195)
Java
with a direct ByteBuffer.
validation failure
java_helpers.h.
Java.
C#
v3.14.0
: Protocol Buffers v3.14.0Compare Source
Protocol Compiler
generating code.
--deterministic_output
toprotoc --encode=...
.C++
any effect.
non-optional fields.
error was encountered.
DebugString.
a single message.
possible. This fixes a lot of warnings when compiling with -Wsign-compare.
libprotoc
separately (#7949)Java
0 bytes when not at EOF.
autoboxing.
@java.lang.Deprecated
if the proto enum has optiondeprecated = true;
.Python
used outside WKT Value/Struct.
PHP
==
operators for Map and Array. (#7900)Go
C#
Javascript
v3.13.0
: Protocol Buffers v3.13.0Compare Source
PHP
better parsing performance and fixes a handful of conformance issues. It will
also make it easier to add support for more features like proto2 and proto3 presence.
version bump. PHP 5.x users can still use pure-PHP.
C++
(for regular messages they were already explicit).
fields.
Python
in EnumTypeWrapper.
Java
not mark the value as present.
C#
This was required to modernize the parsing stack to use the
Span<byte>
type internally. (#7351)
ParseFrom(ReadOnlySequence<byte>)
method to enable GC friendlyparsing with reduced allocations and buffer copies. (#7351)
IBufferWriter<byte>
orto a
Span<byte>
to enable GC friendly serialization.The new API is available as extension methods on the
IMessage
type. (#7576)GOOGLE_PROTOBUF_REFSTRUCT_COMPATIBILITY_MODE
define to makegenerated code compatible with old C# compilers (pre-roslyn compilers
from .NET framework and old versions of mono) that do not support
ref structs. Users that are still on a legacy stack that does
not support C# 7.2 compiler might need to use the new define
in their projects to be able to build the newly generated code. (#7490)
it is recommended to regenerate your generated code to achieve the best
performance (the legacy generated code will still work, but might incur
a slight performance penalty).
v3.12.4
: Protocol Buffers v3.12.4Compare Source
v3.12.2
: Protocol Buffers v3.12.2Compare Source
C++
Objective-C
v3.12.1
: Protocol Buffers v3.12.1Compare Source
Ruby
many people still use them and dropping support will require more
coordination. (#7529, #7531).
v3.12.0
: Protocol Buffers v3.12.0Compare Source
Protocol Compiler
presence tracking. This is enabled by adding the "optional" field label and
passing the
--experimental_allow_proto3_optional
flag to protoc.proto3 presence, see docs/implementing_proto3_presence.md for instructions.
the command-line, to match the behavior when multiple .proto files are passed.
protoc --descriptor_set_out
(#7175)C++
fail when there are missing required fields.
accessor as an easier way of determining if a message is a Well-Known Type.
an "optional" label for a field in a oneof.
Descriptor::extension and DescriptorPool::FindAllExtensions.
protos where this is possible.
Java
getValueDescriptor() on enum special value UNRECOGNIZED instead of
ArrayIndexOutOfBoundsException.
would override the configuration passed into includingDefaultValueFields().
for repeated fields to avoid autoboxing the list contents.
Python
implementation (C++ extension was already doing this).
directly.
JavaScript
PHP
Ruby
C#
on descriptors instead (#7491)
Objective-C
Other
v3.11.4
: Protocol Buffers v3.11.4Compare Source
C#
Ruby
v3.11.3
: Protocol Buffers v3.11.3Compare Source
C++
PHP
v3.11.1
: Protocol Buffers v3.11.1Compare Source
PHP
v3.11.0
: Protocol Buffers v3.11.0Compare Source
C++
Java
Python
JavaScript
PHP
Ruby
C#
Objective C
v3.10.0
: Protocol Buffers v3.10.0Compare Source
C++
Java
This release has a known issue on Android API level <26 (https://github.com/protocolbuffers/protobuf/issues/6718) if you are using
protobuf-java
in Android.protobuf-javalite
users will be fine.Python
JavaScript
PHP
Ruby
Update 2019-10-04: Ruby release has been rolled back due to https://github.com/grpc/grpc/issues/20471. We will upload a new version once the bug is fixed.
Objective C
Other
v3.9.2
: Protocol Buffers v3.9.2Compare Source
Objective-C
v3.9.1
: Protocol Buffers v3.9.1Compare Source
Python
Csharp
v3.9.0
: Protocol Buffers v3.9.0Compare Source
C++
The latter will replace Reflection::FindKnownExtensionByName().
Java
protobuf_java_lite
Bazel target. (#6177)Python
to be in line with claims in C++ implementation (to return first value).
JavaScript
PHP
Ruby