NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules, #285 by repository stars
Latest stable
v1.9.4
Last release 13 days ago
02 Nov 2026
Release timing varies
gaps range from 8 days to 4 months
Nearly every release is documented
notes for 28 of 28 stable releases
Nothing withdrawn
no release was ever pulled
9 years old
206 releases · first in 2017
Drag across the ruler to compare, or tap a release to open it.
This was a failed release attempt. Please ignore this tag and the next. A v1.8.5 will be provided soon.
This was a failed release attempt. Please ignore this tag and the next. A v1.8.5 will be provided soon.
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Several bugs have been addressed in the library used to parse proto source files. Previously grpcurl would accept proto source files that could not ac
grpcurl would accept proto source files that could not actually be compiled with protoc. This release links in the newer version of that library.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.Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
As of this release, binaries are published (to GitHub) for Linux for the ARM64 platform (linux_arm64).
As of this release, binaries are published (to GitHub) for Linux for the ARM64 platform (linux_arm64).
xds:///example.com.optional keyword in proto3 source files (when using -proto arguments). This is a feature that was released in Protocol Buffers v3.15.0 (released as an experimental feature in v3.12.0). You can read more about this language feature here.Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
The NewDefaultEventHandler function has been deprecated. Instead, all fields of grpcurl. DefaultEventHandler are now exported, so you can use a struct…
As of this release, osx_x86_32 binaries will no longer published (for Mac OS X, 32-bit x86/386 architecture). Only 64-bit binaries will be published for OS X.
-vv flag has been added, which enables very verbose output mode. For now, the only additional output will be an estimate of the size of each response message, but more output may be added in the future.grpcurl will now be in the form "grpcurl/<version>" and can also be customized.-user-agent flag has been added, which allows customizing the "User-Agent" request header. The actual header sent will be the given flag value plus " grpcurl/<version>" appended to it.-format-error flag is enabled and an error occurs using service reflection (to download the remote service's descriptors), the error will be formatted in the same machine-friendly format as other RPC errors.NewDefaultEventHandler function has been deprecated. Instead, all fields of grpcurl. DefaultEventHandler are now exported, so you can use a struct literal to initialize a handler instance. This adds Out, Formatter, and Verbosity exported fields to the DefaultEventHandler struct.Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
This replaces the previous function (grpcurl.RequestParserAndFormatterFor), which is now deprecated.
-allow-unknown-fields flag, for more lenient parsing of request JSON. If the input JSON messages contain field names that are unrecognized, they are ignored and the RPC is still made.grpcurl.RequestParserAndFormatter function has been added that accepts grpcurl.FormatOptions to control behavior of the formatter and parser. This replaces the previous function (grpcurl.RequestParserAndFormatterFor), which is now deprecated.Nothing published for this version
Nothing published for this version
Updates support for xDS service discovery to accept "xds" as the URI scheme, in addition to "xds-experimental". Note that the "xds-experimental" schem
Nothing published for this version
Nothing published for this version
Fixes a bug when using -format text where the program would crash when formatting an empty reponse message.
-format text where the program would crash when formatting an empty reponse message.-use-reflection command-line flag. Previously this was true if and only if no -proto or-protoset option were used. This is still the default behavior. But now it can be used with a -proto or -protoset option to use server reflection to resolve the RPC services and schemas but to also provide proto sources to supply message types and extenions that the server may not know about. This can also be used to resolve google.protobuf.Any messages in the response or in RPC error details.-format-error flag which will cause an RPC error to be formatted in a machine-consumable form instead of a human-consumable form. The error will be a google.rpc.Status message representing the error, formatted to stderr as JSON or text, based on the -format in use.grpcurl now indicates the gRPC code of any RPC failure that occurs. The exit code will be 64 plus the numeric value of the error code; so if the RPC fails with an INVALID_ARGUMENT error (code 3), the process will exit with a status of 67. Lower exit codes indicate an error that prevented the RPC from being issued: a code of 2 means a usage error, such as invalid combination of command-line options; a code of 1 indicates some other error occurred, such as being unable to open files or dial a server.Nothing published for this version
Nothing published for this version
This release is only for the Go library. There are no changes to the command-line tool.
This release is only for the Go library. There are no changes to the command-line tool.
"github.com/golang/protobuf/jsonpb/jsonpb_test_proto", which was removed in v1.4 of the protobuf module.Nothing published for this version
Nothing published for this version
The -servername command-line flag is being deprecated. Instead, use -authority, which previously only worked for plain-text invocations, but now works…
GRPC_XDS_BOOTSTRAP environment variable to the path of that file. You can then specify a target using the xds-experimental scheme, like xds-experimental:///example.com (note three slashes). See the gRFC for more details.grpc-encoding: gzip. The grpcurl command-line tool will now correctly handle such compressed responses.grpcurl would send a meta-header of :scheme: http, even when it was using TLS and HTTPS.-servername command-line flag is being deprecated. Instead, use -authority, which previously only worked for plain-text invocations, but now works for all RPCs. Note that this one flag controls both the :authority meta-header and the server name used in SNI when establishing a TLS connection. It is now an error to specify both -authority and -servername with different values.grpcurl.BlockingDial function has been updated to correctly pass :scheme: https meta-header when using TLS. It previously indicated http as the scheme, even when TLS was used.Nothing published for this version
Nothing published for this version
Nothing published for this version
Adds -expand-headers option. This allows secrets to be passed via environment variables instead of on the command-line and then expanded by grpcurl. F
-expand-headers option. This allows secrets to be passed via environment variables instead of on the command-line and then expanded by grpcurl. For example, the following invocation allows the credentials to be supplied in the ACCESS_TOKEN environment variable instead of on the command-line. Notice the use of single quotes, so that the shell does not interpolate the environment variable:grpcurl -expand-headers \
-H 'Authorization: token ${ACCESS_TOKEN}' \
some.endpoint.com:8888 some.Service/Method
-protoset-out option. This instructs grpcurl to save the resolved descriptors (which could be downloaded from a server using service reflection) to a file. The file will be in the same format as those produced by protoc, which is a binary-encoded protocol buffer whose message types is google.protobuf.FileDescriptorSet.grpcurl.ExpandHeaders. This function accepts a slice of header strings and expands ${...} sequences therein, by replacing the sequence with the named environment variable. This can be useful for tools that want to provide the same functionality as grpcurl's -expand-headers flag.grpcurl.WriteProtoset. This function accepts a grpcurl.DescriptorSource for resolving descriptors and a list of symbols to write. It writes the file descriptors that contain the given symbols, as well as the transitive dependencies of those files.This fixes an issue in the go.mod file that would prevent earlier versions from working with modules when using Go 1.13.
This fixes an issue in the go.mod file that would prevent earlier versions from working with modules when using Go 1.13.
Since this change only impacts users that are building from source and does not actually impact the resulting binary, this release does not include pre-compiled artifacts. See v1.3.1 for the latest binaries.
This release fixes a bug that required -proto arguments be relative to the current working directory. Releases prior to v1.3.0 allow arguments to inst
-proto arguments be relative to the current working directory. Releases prior to v1.3.0 allow arguments to instead be relative to a path named by an -import_path argument. Now -proto arguments can be paths that are relative to either an -import_path argument or the current working directory. The import paths will be preferred, earlier arguments taking precedence over later ones, in the event of ambiguity (i.e. if the relative path matches both a file under an import path and a file under the current working directory).If the server sends back an error that includes error details (in the form of optional google.protobuf.Any messages), grpcurl previously did not displ
google.protobuf.Any messages), grpcurl previously did not display them, only showing the code and message. Now the details will be included, formatted in either JSON or the protobuf text format, depending on the -format flag (which defaults to JSON). If grpcurl cannot decode the message because the embedded message type is not known, it will format it as JSON with a special "@value" property that shows the encoded bytes.-proto and -import-path flags, to load the RPC schema from proto sources, the tool would get confused and likely produce errors if any absolute paths were provided. Now the loading of proto sources works much more like protoc, regarding how file names are resolved based on import paths and relative vs. absolute paths.grpcurl.DescriptorSourceFromProtoFiles method would get confused and typically return confusing errors if given absolute paths for the proto file names to parse. This now uses protoparse.ResolveFilenames (from the https://github.com/jhump/protoreflect repo) so that resolving the given paths to files on the file system behaves more like protoc.grpcurl.PrintStatus has been aded that prints the results of an RPC to a given io.Writer. The content written includes a human-readable description of the RPC error code, the error message, and any detail messages (if present).jsonpb.AnyResolver implementations that are backed by a grpcurl.DescriptorSource:
grpcurl.AnyResolverFromDescriptorSource: uses the given grpcurl.DescriptorSource to resolve message names in Any messages.grpcurl. AnyResolverFromDescriptorSourceWithFallback : the same as the above method except that if the message cannot be resolved via the grpcurl.DescriptorSource, the returned message will be a special message that will format to JSON similarly to a normal google.protobuf.Any message but with a special "@value" attribute that contains the embedded, encoded message bytes.Nothing published for this version
This release fixes a few issues related to JSON handling when processing user-provided request data and when printing server response data:
This release fixes a few issues related to JSON handling when processing user-provided request data and when printing server response data:
google.protobuf.Value or google.protobuf.ListValue and the data that grpcurl wanted to send was a "null" value or "[]" empty list (respectively), grpcurl would raise an error, being unable to unmarshal the request data correctly.-emit-defaults flag were used.-emit-defaults flag were used, all fields of the oneof would be shown, with the unset fields indicating a zero/default value.NOTE: Prefer v1.2.1 over this release. This one was the result of pushing the v1.2.0 tag prematurely.
NOTE: Prefer v1.2.1 over this release. This one was the result of pushing the v1.2.0 tag prematurely.
-max-msg-sz flag, to set the maximum size of a response message that grpcurl will accept. This was previously hard-coded to 4mb, so now grpcurl can be used with larger messages.grpcurl.BlockingDial function was used to create a long-lived connection, the resulting *grpc.ClientConn would become unusable if the dial context was cancelled (or expired) AND the underlying socket was disconnected and needed to reconnect (such as if the server were restarted). This is now fixed.Nothing published for this version
Nothing published for this version
Deprecates InvokeRpc and RequestMessageSupplier. Instead, use InvokeRPC and RequestSupplier.
-version flag, to print the current version of grpcurl.-format flag which supports using protobuf text format instead of JSON as input and output data format.describe verb will print elements as proto source instead of JSON representations of descriptor protos. This greatly aids readability of the output.InvokeRpc and RequestMessageSupplier. Instead, use InvokeRPC and RequestSupplier.GetAllFiles function, for trying to load all known file descriptors for a descriptor source.GetDescriptorText now uses protobuf syntax instead of JSON. So a message descriptor will look like the message definition in proto source instead of a JSON representation of the descriptor proto.Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Initial release using semver versioning scheme, including support for Go modules.
Initial release using semver versioning scheme, including support for Go modules.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.