protobuf-go/go.mod

module google.golang.org/protobuf

go 1.9

require (
	github.com/golang/protobuf v1.4.1
	github.com/google/go-cmp v0.5.0
)
go.mod, go.sum: add back in after v2 module renaming Change-Id: Iba5d25391870b4a6014fd90fc79ab101c75ea3c7 Reviewed-on: https://go-review.googlesource.com/c/protobuf/+/177042 Reviewed-by: Joe Tsai <thebrokentoaster@gmail.com> 2019-05-14 18:18:06 +00:00			`module google.golang.org/protobuf`

			`go 1.9`

all: depend on github.com/golang/protobuf@1.4.0-rc1 While this module has no actual dependency on APIv1, we want to ensure that programs using both APIv1 and APIv2 use a version of APIv1 that wraps APIv2. Updates golang/protobuf#1032. Change-Id: Ie69ce2930c843a7232c79b21ff418c53b28ed1af Reviewed-on: https://go-review.googlesource.com/c/protobuf/+/219382 Reviewed-by: Joe Tsai <joetsai@google.com> 2020-02-13 23:20:57 +00:00			`require (`
all: add weak dependency on google.golang.org/genproto module This is step 4 of 6 in a multi-stage migration to move the well-known types from the google.golang.org/genproto module to the google.golang.org/protobuf module. The generated Go packages for field_mask.proto, api.proto, type.proto, and source_context.proto are being moved over to this module alongside all the other well-known types. In order to move these types between two modules, there needs to be a sequence of changes submitted in decently rapid succession. It is impossible to atomically make these changes, so a brief breakage is inevitable. The steps are as follows: Step 1: Submit a change to cloud.google.com/go/internal/gapicgen to avoid generating the well-known types. Otherwise, the tool will undo the changes made in step 3. See https://code-review.googlesource.com/c/gocloud/+/56810 Step 2: Submit a change to google.golang.org/protobuf that adds the generated well-known types being migrated to that module. In order to prevent the situation where a user links in too old a version of the genproto module such that duplicate registration occurs for the well-known types, the registry is specially modified to provide an error message that instructs users to upgrade the genproto module. See https://golang.org/cl/234937 Step 3: Submit a change to google.golang.org/genproto that switches all generated well-known types to be aliases to the ones declared in google.golang.org/protobuf from the previous step. This will cause the genproto module to incur an dependency on an unreleased version of the protobuf module. See https://github.com/googleapis/go-genproto/pull/372 Step 4: Submit a change to google.golang.org/protobuf that adds a weak module depdency on the genproto module at the revision from the previous step. See https://golang.org/cl/235297 Step 5: Release google.golang.org/protobuf@v1.24.0. See https://golang.org/cl/235299 Step 6: Submit a change to google.golang.org/genproto that updates the protobuf module dependency to v1.24.0. Change-Id: I22d496e7496446becad742eab05b169abb735ae2 Reviewed-on: https://go-review.googlesource.com/c/protobuf/+/235297 Reviewed-by: Damien Neil <dneil@google.com> 2020-05-26 20:30:59 +00:00			`github.com/golang/protobuf v1.4.1`
all: update to cmp@v0.5.0 release Change-Id: If2f6cd6b4ad63a60ad19df8602cc97cca92e5a10 Reviewed-on: https://go-review.googlesource.com/c/protobuf/+/238757 Reviewed-by: Herbie Ong <herbie@google.com> 2020-06-18 16:34:13 +00:00			`github.com/google/go-cmp v0.5.0`
all: depend on github.com/golang/protobuf@1.4.0-rc1 While this module has no actual dependency on APIv1, we want to ensure that programs using both APIv1 and APIv2 use a version of APIv1 that wraps APIv2. Updates golang/protobuf#1032. Change-Id: Ie69ce2930c843a7232c79b21ff418c53b28ed1af Reviewed-on: https://go-review.googlesource.com/c/protobuf/+/219382 Reviewed-by: Joe Tsai <joetsai@google.com> 2020-02-13 23:20:57 +00:00			`)`