ojo-network / ojo

Apache License 2.0
52 stars 28 forks source link

chore(deps): bump google.golang.org/grpc/cmd/protoc-gen-go-grpc from 1.3.0 to 1.5.1 #491

Open dependabot[bot] opened 1 month ago

dependabot[bot] commented 1 month ago

Bumps google.golang.org/grpc/cmd/protoc-gen-go-grpc from 1.3.0 to 1.5.1.

Release notes

Sourced from google.golang.org/grpc/cmd/protoc-gen-go-grpc's releases.

protoc-gen-go-grpc v1.5.1

Dependencies

  • Removed replace directive (needed only for testing), since it is incompatible with go install (#7451).

protoc-gen-go-grpc v1.5.0

Security

  • The generated function Register<Service>Server now panics if the Unimplemented<Service>Server struct is embedded in a way that would otherwise lead to runtime panics if an unimplemented method was called. Users are advised to ensure they are properly embedding the Unimplemented struct for their service, and to regenerate their proto files to confirm. (#7438)
    • Note: "Proper embedding" of the Unimplemented struct means either embedding the struct by value (preferred) or ensuring it is always initialized to a valid pointer. E.g.
struct MyServiceImpl {
    pb.UnimplementedMyServiceServer // embedded by value, not pointer
    // .. other struct fields ..
}

New Features

  • Generated code for services will produce streaming method definitions using one of six different generic types (e.g. BidiStreamingServer or ClientStreamingClient) instead of producing complete interfaces and implementations for the streaming methods. This can be disabled by setting use_generic_streams_experimental=false. Please file a bug if you encounter any issues with this behavior. (#7387)

Bug Fixes

  • A period (.) is added to the end of the service interface doc comment to comply with Godoc. (#7392)

protoc-gen-go-grpc v1.4.0

New Features

  • Add an optional implementation of streams using generics (Experimental) (#7057)
    • The new use_generic_stream_experimental=true option will cause the gRPC codegen to use prebuilt generic types to implement client and server stream objects, rather than generating new types and implementations for every RPC method. We intend to transition this to the default behavior in the next release. Please test it and provide any feedback.
    • Special Thanks: @​aarongable
  • Copy service comments to interfaces in generated code (#7243)
  • Generated code includes static method gRPC call options for integration with the upcoming OpenTelemetry metrics support (#6960)

Dependencies

Commits


Dependabot compatibility score

You can trigger a rebase of this PR by commenting @dependabot rebase.


Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note Automatic rebases have been disabled on this pull request as it has been open for over 30 days.