Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

deps: update dependency to v3.13.0 #273

merged 1 commit into from Sep 23, 2020


Copy link

@renovate-bot renovate-bot commented Aug 15, 2020

This PR contains the following updates:

Package Update Change (source) minor 3.12.4 -> 3.13.0

Release Notes



Compare Source


  • The C extension is completely rewritten. The new C extension has significantly
    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.
  • The new C extension does not support PHP 5.x, which is the reason for the major
    version bump. PHP 5.x users can still use pure-PHP.


  • Removed deprecated unsafe arena string accessors
  • Enabled heterogeneous lookup for std::string keys in maps.
  • Removed implicit conversion from StringPiece to std::string
  • Fix use-after-destroy bug when the Map is allocated in the arena.
  • Improved the randomness of map ordering
  • Added stack overflow protection for text format with unknown fields
  • Use std::hash for proto maps to help with portability.
  • Added more Windows macros to proto whitelist.
  • Arena constructors for map entry messages are now marked "explicit"
    (for regular messages they were already explicit).
  • Fix subtle aliasing bug in RepeatedField::Add
  • Fix mismatch between MapEntry ByteSize and Serialize with respect to unset


  • JSON format conformance fixes:
    • Reject lowercase t for Timestamp json format.
    • Print full_name directly for extensions (no camelCase).
    • Reject boolean values for integer fields.
    • Reject NaN, Infinity, -Infinity that is not quoted.
    • Base64 fixes for bytes fields: accept URL-safe base64 and missing padding.
  • Bugfix for fields/files named "async" or "await".
  • Improved the error message when AttributeError is returned from getattr
    in EnumTypeWrapper.


  • Fixed a bug where setting optional proto3 enums with setFooValue() would
    not mark the value as present.
  • Add Subtract function to FieldMaskUtil.


  • Dropped support for netstandard1.0 (replaced by support for netstandard1.1).
    This was required to modernize the parsing stack to use the Span<byte>
    type internally. (#​7351)
  • Add ParseFrom(ReadOnlySequence<byte>) method to enable GC friendly
    parsing with reduced allocations and buffer copies. (#​7351)
  • Add support for serialization directly to a IBufferWriter<byte> or
    to a Span<byte> to enable GC friendly serialization.
    The new API is available as extension methods on the IMessage type. (#​7576)
    generated 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)
  • Due to the major overhaul of parsing and serialization internals (#​7351 and #​7576),
    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).

Renovate configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by WhiteSource Renovate. View repository job log here.

@trusted-contributions-gcf trusted-contributions-gcf bot added the kokoro:run label Aug 15, 2020
@google-cla google-cla bot added the cla: yes label Aug 15, 2020
@yoshi-kokoro yoshi-kokoro removed the kokoro:run label Aug 15, 2020
Copy link

@codecov codecov bot commented Aug 15, 2020

Codecov Report

Merging #273 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff            @@
##             master     #273   +/-   ##
  Coverage     67.68%   67.68%           
  Complexity      374      374           
  Files            34       34           
  Lines          1897     1897           
  Branches        266      266           
  Hits           1284     1284           
  Misses          508      508           
  Partials        105      105           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update df518d3...d153c18. Read the comment docs.

@trusted-contributions-gcf trusted-contributions-gcf bot added the kokoro:run label Aug 17, 2020
@renovate-bot renovate-bot force-pushed the renovate/protobuf.version branch from 9d9d93d to 54f1ff9 Compare Aug 27, 2020
@trusted-contributions-gcf trusted-contributions-gcf bot added the kokoro:force-run label Aug 27, 2020
@yoshi-kokoro yoshi-kokoro removed kokoro:run kokoro:force-run labels Aug 27, 2020
@renovate-bot renovate-bot force-pushed the renovate/protobuf.version branch from 54f1ff9 to d153c18 Compare Sep 23, 2020
@renovate-bot renovate-bot requested a review from as a code owner Sep 23, 2020
@trusted-contributions-gcf trusted-contributions-gcf bot added the kokoro:force-run label Sep 23, 2020
@yoshi-kokoro yoshi-kokoro removed the kokoro:force-run label Sep 23, 2020
@chingor13 chingor13 merged commit 4476f33 into googleapis:master Sep 23, 2020
16 of 17 checks passed
@renovate-bot renovate-bot deleted the renovate/protobuf.version branch Sep 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
cla: yes
None yet

Successfully merging this pull request may close these issues.

None yet

3 participants