v1.9.1

Changelog

• 400fa5f Update Dockerfile to use Go v1.21 (#455)
• 0e13e85 chore: fix some typos in comments (#454)

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

• 07361b2 Use latest protoreflect to fix some bugs (#453)
• 8e76884 Brand name update (#452)
• 805ce40 Bump github.com/golang/protobuf from 1.5.3 to 1.5.4 (#448)
• 93ea011 goreleaser: bump version & add nfmp support (#440)
• 5592211 Enable xDS credentials (#424)
• 184c8f7 Bump github.com/jhump/protoreflect from 1.15.5 to 1.15.6 (#446)
• 149a93e Use localhost for default unix domain socket authority (#445)
• 252b57f Bump github.com/jhump/protoreflect from 1.15.4 to 1.15.5 (#443)
• 24b80df Added initial support for -t flag to show timings (#428)
• 334e3f5 Expand the documentation of -max-time to clarify this sets the RPC timeout (#435)
• f415774 Bump github.com/jhump/protoreflect from 1.15.3 to 1.15.4 (#436)
• 79fb35f Bump google.golang.org/protobuf from 1.31.0 to 1.32.0 (#437)
• 7ccaf0a indent: rip out old go 1.9 support
• 6093b09 Bump golang.google.org/grpc to v1.57.1 (#427)
• 70c215f Update Tarball URL used by Homebrew (#421)

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

• 42f6302 Update go.mod, goreleaser for v1.8.8 (#413)
• 743e60a Run tests on Go 1.21 (#408)
• b7a5d3b Update protoreflect v1.15.2 and grpc v1.57.0 (#406)
• 2a29c1e Use grpc.reflection.v1.ServerReflection (#407)
• 9a59bed Bump google.golang.org/protobuf from 1.30.0 to 1.31.0 (#401)
• ae7dadf Bump google.golang.org/grpc from 1.55.0 to 1.56.1 (#400)
• 3961a33 Fix issues with error details (#379)
• d5b8e4d fix nil-dereference panic (#395)
• 0efcfa6 Bump google.golang.org/grpc from 1.54.0 to 1.55.0 (#390)
• fae5880 Add "checkgenerate" make target to CI (#385)
• 1fda47e Bump google.golang.org/grpc from 1.53.0 to 1.54.0 (#383)
• 031cd3d Bump google.golang.org/protobuf from 1.29.1 to 1.30.0 (#378)
• a5037bd Bump google.golang.org/protobuf from 1.29.0 to 1.29.1 (#376)
• 4775fb5 Bump google.golang.org/protobuf from 1.28.1 to 1.29.0 (#375)
• b96cb4d Bump github.com/golang/protobuf from 1.5.2 to 1.5.3 (#374)
• 0069181 Bump google.golang.org/grpc from 1.52.3 to 1.53.0 (#370)
• 66a2405 Install the CodeSee workflow. Learn more at https://docs.codesee.io (#368)
• dfd889a Bump google.golang.org/grpc from 1.51.0 to 1.52.3 (#365)
• a3a5bcd Bump github.com/jhump/protoreflect from 1.14.0 to 1.14.1 (#361)
• 61a9c00 Bump google.golang.org/grpc from 1.50.1 to 1.51.0 (#348)
• 85f1cbf fix funcname in comment (#346)
• dd2f601 Bump github.com/jhump/protoreflect from 1.13.0 to 1.14.0 (#343)
• 81c624c Bump google.golang.org/grpc from 1.50.0 to 1.50.1 (#338)
• 3826617 Bump google.golang.org/grpc from 1.49.0 to 1.50.0 (#336)
• 8d60b61 Bump github.com/jhump/protoreflect from 1.12.0 to 1.13.0 (#335)
• 47b842a Bump google.golang.org/grpc from 1.48.0 to 1.49.0 (#330)
• 898bdad fixup release process (#328)

v1.8.7

Changes

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

Changelog

• 0d0992e Add go 1.18 support; set Dockerfile to go 1.18 (#325)
• 8093376 build alpine base image (#311)
• fec466e fix some typos (#314)
• 7f919e6 Bump google.golang.org/grpc from 1.47.0 to 1.48.0 (#324)
• 0df5c93 Adding power(ppc64le) arch support (#296)
• 353e095 Enable support for Unix sockets for Windows by enabling -unix flag for Windows builds. (#317)
• c9ac3da Bump google.golang.org/grpc from 1.46.2 to 1.47.0 (#315)
• ea24a77 Bump github.com/jhump/protoreflect from 1.10.3 to 1.12.0 (#294)
• c3fbeaf Bump google.golang.org/grpc from 1.44.0 to 1.46.2 (#310)
• 7860209 Bump google.golang.org/protobuf from 1.27.1 to 1.28.0 (#298)
• b953ea1 use newer goreleaser (#293)
• 683a7fb Restore support for linux/s390x for the next release. (#292)
• 8bb6eeb Bump google.golang.org/protobuf from 1.26.0 to 1.27.1 (#288)

v1.8.6

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

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

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

v1.8.3 - DO NOT USE

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

v1.8.2

Changes

Command-line tool

• Several 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. This release links in the newer version of that library.

Go package "github.com/fullstorydev/grpcurl"

• Callers of grpcurl.BlockingDial can now supply the dial option grpc.FailOnNonTempDialError(false), to prevent the fast-fail behavior for certain kinds of errors (such as "connection refused"). Previously, even if this option were provided, it would be ignored/overwritten by other options that BlockingDial uses.