GitHub

v1.9.3

Changelog

v1.9.2

Changelog

v1.9.1

Changelog

v1.9.0

Notes

  • An issue during the release of this version prevented the Dockerfiles from being created. If you're an user of grpcurl images, or via Brew, please use the release v1.9.1.

Changelog

v1.8.9

Changelog

  • 28c0ee2 Disable CGO for improved compatibility across distros (#420)
  • bc2944d Bump golang.org/x/net from 0.9.0 to 0.17.0 (#419)
  • 7a845ca SIGSEGV: panic: runtime error: invalid memory address or nil pointer dereference in protoreflect (#416)
  • c17f078 Added alts credential option (#341)

v1.8.8

Changelog

v1.8.7

Changes

  • Unix sockets for windows
  • Lots of dependency version updates
  • Support for Go 1.18

Changelog

v1.8.6

@jhump jhump released this

08 Feb 21:59

Changes

Command-line tool

  • Some bugs have been addressed in the library used to parse proto source files. Previously grpcurl would accept proto source files that could not actually be compiled with protoc. The converse could also happen: grpcurl could reject some proto source files that could successfully be compiled with protoc. More details can be found in the release notes for the changes to the protoparse library, versions v1.10.2 and v1.10.3.
  • Some implementations of the server reflection service have been observed to return multiple (even superfluous) file descriptors, in response to requests made by grpcurl. These extra files, if not returned in a particular order, would cause grpcurl to report an error that the service or method to be invoked could be not be resolved. The reflection client in grpcurl is now more robust to this condition and can handle responses with file descriptors in any order, so it should be interoperable with a larger variety of servers.
  • When a request message includes a field of type google.protobuf.Value and a value for that field that was a JSON array, grpcurl would incorrectly interpret the JSON array as if it were a single atomic value, the last value that was in the array. This has been fixed.
  • When a response message includes non-printable characters or code points outside the ASCII 7-bit range in the name of a field in a JSON object, it could be improperly encoded with escape characters that are not valid JSON. Standard tools/libraries could then fail to parse the JSON output from grpcurl. This has been fixed.

v1.8.5

@jhump jhump released this

07 Oct 20:38

This is the first release that includes binaries for linux/s390x. This is also the first release that includes Docker images for arm platforms (we hope to add Docker images for s390x in the future).

Changes

Command-line tool

  • Some bugs have been addressed in the library used to parse proto source files. Previously grpcurl would accept proto source files that could not actually be compiled with protoc. The converse could also happen: grpcurl could reject some proto source files that could successfully be compiled with protoc. More details can be found in the release notes for the changes to the protoparse library, versions v1.10.0 and v1.10.1.
  • Some error conditions could cause grpcurl to "panic", where the tool aborts with a stack dump. These could be induced by providing proto source files with certain unusually high unicode code points (which would not actually be valid protobuf source). It could also be induced by unlucky timing of connectivity failure to RPC server when making a client-streaming or bidi-streaming RPC.
  • Adds support for specifying an environment variable SSLKEYLOGFILE, which indicates a file name. When set and using TLS for a connection, grpcurl will log the TLS key used, so that an external tool such as Wireshark can use the key to decrypt and inspect network packets.

Go package "github.com/fullstorydev/grpcurl"

  • Goroutines calling grpcurl.InvokeRPC could panic when calling client-streaming and bidi-streaming methods, if the stream could not be created (such as a connectivity issue). This panic has been fixed and an error will be returned instead.

v1.8.4 - DO NOT USE

Pre-release

@jhump jhump released this

07 Oct 20:32

This was a failed release attempt. Please ignore this tag. A v1.8.5 will be provided soon.

Read the original on github.com ↗