NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules, #1341 by repository stars
Latest stable
v1.19.0
Last release 1 months ago
05 Oct 2026
Ships unpredictably
gaps range from 2 weeks to 1.4 years
Nearly every release is documented
notes for 39 of 39 stable releases
Nothing withdrawn
no release was ever pulled
10 years old
353 releases · first in 2017
Drag across the ruler to compare, or tap a release to open it.
Nothing published for this version
Nothing published for this version
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
This release contains many bug fixes.
This release contains many bug fixes.
Changes/fixes:
json_name attribute, instead of using the proto field name, the library now falls back to computing a default JSON name in the same manner as protoc. This is necessary since descriptors that are generated into Java code by protoc, for example, do not have the attribute present unless the option was explicitly present in the source.Changes/fixes:
Changes/fixes:
protoc.
option (custom.option).(some.extension) = "foo";
However, protoparse would fail with a syntax error upon seeing the second open parenthesis. This is now fixed.max, the actual end tag encoded in the descriptor was wrong and did not represent the full allowed range for message set encoding. This is now fixed.syntax = "proto2"). And groups can have options. However protoparse rejected definitions of groups with options that were inside of a oneof. This is now fixed.syntax = "proto2"). However, protoparse mistakenly rejected oneofs, stating they had to have at least one field. This is now fixed.reserved statements in messages and enums failed to identify duplicate reserved names in some cases. This is now fixed.Changes/fixes:
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
Nothing published for this version
Nothing published for this version
Nothing published for this version
Support was added for groups that have field options. This is a lesser-known feature of groups (which is a technically deprecated feature of the proto…
This release contains bug fixes and new features/APIs.
Changes/fixes:
Buffer.EncodeFieldValue method will now use always packed encoding for repeated fields that are so configured. Previously, it only used packed encoding when the repeated field actually contained more than one value.Additions:
Parser struct has a new field named LookupImport. When set, if an imported file cannot be loaded via the parser's Accessor, this field will be invoked. Unlike Accessor, this field supplies an already parsed descriptor instead of protobuf source code to parse. This allows for parsed files' dependencies to provided in already-parsed descriptor form instead of having to re-parse said dependencies.Changes/fixes:
ResolveFilenames function has been modified so it should work as expected/documented on Windows platforms, not just platforms that use forward slash (/) as a path separator.message Foo {
optional group Bar = 1 [(field.option) = "baz1"] {
option (msg.option) = "baz2";
}
}
This package now provides the same level of support for this as does protoc. Earlier versions of this package would have reported a syntax error at the opening bracket ([) of the field options.Changes/fixes:
Changes/fixes:
"), the resulting text output would be invalid and unparseable. This has been fixed.KnownTypeRegistry should now correctly identify well-known types when using generated types in v2 of the protobuf module.nil value (e.g. the value type is a message and the value stored in the map is a nil pointer), the operation would panic. Now it serializes that map entry with no value (e.g. the synthetic message representing the map entry will be serialized with only a key and omit the value field). This is how the protobuf module's proto package handles this scenario in generated messages with map fields.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
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
This release contains bug fixes and new features/APIs.
This release contains bug fixes and new features/APIs.
This release also fixes the repo's go.mod file to be compatible with Go 1.13.
Additions:
Buffer type that provides API for interacting with the protobuf binary format. This makes it easy to write programs that can dynamically emit or consume a stream of protobuf-encoded data.Additions:
CreateFileDescriptorsFromSet function. This is a convenience method around CreateFileDescriptors when the source of descriptors is a *FileDescriptorSet.Changes/fixes:
BuilderOptions had to be used with a custom extension registry, or else those custom options would not make it into the built descriptor. Now, the custom option can be defined in the file being built or in any of its dependencies, and they will successfully be interpreted and retained. This means that BuilderOptions.Extensions should no longer be needed in most cases.FileBuilder: AddDependency and AddImportedDependency, which allow explicitly adding imports to the file. These can be used during building to resolve custom options.FromFile to convert and existing file descriptor into a builder and then building the result, the output descriptor would strip unused imports from the file. This is no longer the case, so that some imports that are only used to define custom options can be retained and custom options correctly interpreted.Additions:
ErrorReporter type and eponymous name on the Parser struct have been added. When the field is unset, the behavior matches previous versions. When set, the reporter will be called for each error encountered, and parsing may continue, allowing a single parse invocation to report many errors instead of failing after the first one.ErrorWithPos interface is provided to represent an error that includes source position. The type of errors returned by the parser were previously unspecified, but were often instances of the concrete exported type *ErrorWithSourcePos. Code that inspected errors and attempted type assertions to this type should instead type assert to this new interface as errors returned by the parser in the future may not be of this concrete type, but may still contain source position information.Changes/fixes:
allow_alias options for enums. This is fixed.protoparse and the files being compiled used the package's copy of standard imports (such as google/protobuf/timestamp.proto et al), when the race detector was enabled, it was possible for it to be tripped. The race should be harmless in practice since the writes that trigger the race are actually no-ops, so it is mainly an issue when running tests with the race detector enabled. This has been fixed: concurrent invocations of protoparse no longer share a copy of these standard imports. Instead, they are cloned for each invocation to use safely.protoc. Here are the most significant variances that were addressed:
protoc's order.protoc.protoc generates source info for extension blocks.protoc. For example, protoc emits multiple entries for the path option (without an index), one for each actual option declared in the file. This package now does the same.protoc's logic, which assumes that tab stops are 8 characters apart.protoc does. Instead of returning an error, it will return an empty descriptor.UninterpretedOptions fields in options messages of descriptors produced by this package will now be nil when all options are interpreted. Previously, the field was set to an empty slice, which caused confusing/noisy output if the descriptor were then marshaled to JSON via the golang.org/protobuf/jsonpb package.Changes/fixes:
Changes/fixes:
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
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
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
This release contains bug-fixes for a single function.
This release contains bug-fixes for a single function.
Changes/fixes:
ResolveFilenames function previously expected file paths to always be relative to the process's current working directory. However, correct behavior (modeled after protoc) is to also allow file paths to be relative to one of the import paths. This has been fixed: file paths are only assumed to be relative to cwd when no such file exists that is relative to one of the import paths.ResolveFilenames function could get confused if provided paths that included symbolic links. When deciding whether or not one absolute path is a descendant of another (part of its logic to relate file paths with their corresponding import path), paths will now be canonicalized by resolving symbolic links.This release just contains one small change.
This release just contains one small change.
Changes/fixes:
protoparse.ErrorWithSourcePos. Previously, if it happened when processing a given file's dependencies, the error would be wrapped and no longer be the right type, thus obscuring access to the source location of the error.Nothing published for this version
This release contains just bug fixes.
This release contains just bug fixes.
Changes/fixes:
Changes/fixes:
This package will now accept multi-line type references, as long as any whitespace (including newlines) appears between a component of a qualified name and the subsequent dot (.). For example, the following source would now be accepted (but previously would not):
syntax = "proto3";
import "google/protobuf/empty.proto";
message Foo {
google
.protobuf
.Empty bar = 1;
}
When parsing either a well-known import (files included with protoc that have a "google/protobuf" import path) or a file that imports a well-known import, parsing would fail if the well-known import itself had any dependencies. This means that trying to parse any of the following (or files that imported any of the following) would return an error indicating unrecognized symbols:
google/protobuf/api.protogoogle/protobuf/type.protogoogle/protobuf/compiler/plugin.protoThis issue is fixed, and parsing the above well-known imports now works.
Changes/fixes:
ComputeUrl method of type *msgregistry.MessageRegistry would return incorrect results for types that were explicitly added via the AddMessage, AddEnum, or AddFile methods. This has been fixed.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.