status-im/consul
2
0
Fork 0
mirror of https://github.com/status-im/consul.git synced 2025-01-22 19:50:36 +00:00
Code Issues Projects Releases Wiki Activity
consul/proto-public/go.mod

17 lines
388 B
Modula-2
Raw Normal View History

Make proto-public a Go module Our original intention was for projects to consume and generate their own Go code for these protobuf packages using Buf. While this is still the best route for many projects, it causes some headaches when using a library (e.g. consul-server-connection-manager) that pulls in the same protobuf package as your project, as Go's protobuf implementation only allows for a package/namespace to be registered once. In such cases, projects can depend on this Go module instead, as a single place where these protobuf packages are registered.
2022-09-06 18:46:56 +01:00
module github.com/hashicorp/consul/proto-public
go 1.19
require (
[NET-6138] security: Bump `google.golang.org/grpc` to 1.56.3 (CVE-2023-44487) (#19414) Bump google.golang.org/grpc to 1.56.3 This resolves [CVE-2023-44487](https://nvd.nist.gov/vuln/detail/CVE-2023-44487). Co-authored-by: Chris Thain <chris.m.thain@gmail.com>
2023-10-30 08:44:22 -04:00
google.golang.org/grpc v1.56.3
security: upgrade google.golang.org/protobuf to 1.33.0 (#20801) Resolves CVE-2024-24786.
2024-03-06 18:04:42 -05:00
google.golang.org/protobuf v1.33.0
Make proto-public a Go module Our original intention was for projects to consume and generate their own Go code for these protobuf packages using Buf. While this is still the best route for many projects, it causes some headaches when using a library (e.g. consul-server-connection-manager) that pulls in the same protobuf package as your project, as Go's protobuf implementation only allows for a package/namespace to be registered once. In such cases, projects can depend on this Go module instead, as a single place where these protobuf packages are registered.
2022-09-06 18:46:56 +01:00
)
require (
security: upgrade google.golang.org/protobuf to 1.33.0 (#20801) Resolves CVE-2024-24786.
2024-03-06 18:04:42 -05:00
github.com/golang/protobuf v1.5.4 // indirect
security: bump go, x/net and envoy versions (#20956) * Bump go version * Bump x/net * Bump envoy version * Add changelog --------- Co-authored-by: Michael Zalimeni <michael.zalimeni@hashicorp.com>
2024-04-08 15:18:40 -04:00
golang.org/x/net v0.24.0 // indirect
golang.org/x/sys v0.19.0 // indirect
[NET-7009] security: update x/crypto to 0.17.0 (#20023) security: update x/crypto to 0.17.0 This addresses CVE-2023-48795 (x/crypto/ssh).
2023-12-21 15:11:19 -05:00
golang.org/x/text v0.14.0 // indirect
Various bits of cleanup detected when using Go Workspaces (#17462) TLDR with many modules the versions included in each diverged quite a bit. Attempting to use Go Workspaces produces a bunch of errors. This commit: 1. Fixes envoy-library-references.sh to work again 2. Ensures we are pulling in go-control-plane@v0.11.0 everywhere (previously it was at that version in some modules and others were much older) 3. Remove one usage of golang/protobuf that caused us to have a direct dependency on it. 4. Remove deprecated usage of the Endpoint field in the grpc resolver.Target struct. The current version of grpc (v1.55.0) has removed that field and recommended replacement with URL.Opaque and calls to the Endpoint() func when needing to consume the previous field. 4. `go work init <all the paths to go.mod files>` && `go work sync`. This syncrhonized versions of dependencies from the main workspace/root module to all submodules 5. Updated .gitignore to ignore the go.work and go.work.sum files. This seems to be standard practice at the moment. 6. Update doc comments in protoc-gen-consul-rate-limit to be go fmt compatible 7. Upgraded makefile infra to perform linting, testing and go mod tidy on all modules in a flexible manner. 8. Updated linter rules to prevent usage of golang/protobuf 9. Updated a leader peering test to account for an extra colon in a grpc error message.
2023-06-05 16:08:39 -04:00
google.golang.org/genproto v0.0.0-20230410155749-daa745c078e1 // indirect
Make proto-public a Go module Our original intention was for projects to consume and generate their own Go code for these protobuf packages using Buf. While this is still the best route for many projects, it causes some headaches when using a library (e.g. consul-server-connection-manager) that pulls in the same protobuf package as your project, as Go's protobuf implementation only allows for a package/namespace to be registered once. In such cases, projects can depend on this Go module instead, as a single place where these protobuf packages are registered.
2022-09-06 18:46:56 +01:00
)
Reference in New Issue Copy Permalink