Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v0.7.3
->v0.8.0
v2.1.0
->v2.2.0
v1.68.1
->v1.69.0
Release Notes
bufbuild/protovalidate-go (github.com/bufbuild/protovalidate-go)
v0.8.0
Compare Source
Breaking Change: The
protovalidate.ValidationError
type is no longer a protobufbuf.validate.Violations
message alias, but a struct containing a slice ofprotovalidate.Violation
instances. In most cases, accessing theProto
member of the violation is all that needs to be done:protovalidate.ValidationError
still has aToProto()
method that returns the protobufbuf.validate.Violations
message equivalent.The new
protovalidate.Violation
structure contains additional in-memory information about the violation which cannot be serialized to the wire:FieldValue
: Aprotoreflect.Value
containing the value of the field failing validation, if there is a field corresponding to the violation.FieldDescriptor
: Aprotoreflect.FieldDescriptor
corresponding to the field failing validation.RuleValue
: Aprotoreflect.Value
containing the value of the rule failing validation, if there is a rule corresponding to the violation.RuleDescriptor
: Aprotoreflect.FieldDescriptor
corresponding to the rule failing validation.Take, for example, the following protobuf message schema:
If you try to validate the struct
pb.User{Email: "invalid"}
, theFieldValue
will be"invalid"
and theRuleValue
will betrue
.Some violations do not correspond directly to a field, such as a message constraint failure; in these cases, the
FieldValue
will be an invalid value and theFieldDescriptor
will benil
.What's Changed
Full Changelog: bufbuild/protovalidate-go@v0.7.3...v0.8.0
grpc-ecosystem/go-grpc-middleware (github.com/grpc-ecosystem/go-grpc-middleware/v2)
v2.2.0
Compare Source
What's Changed
New Contributors
Full Changelog: grpc-ecosystem/go-grpc-middleware@v2.1.0...v2.2.0
grpc/grpc-go (google.golang.org/grpc)
v1.69.0
: Release 1.69.0Compare Source
Known Issues
grpc.NewClient
function is incompatible with forward proxies, because it resolves the target hostname on the client instead of passing the hostname to the proxy. A fix is expected to be a part of grpc-go v1.70. (#7556)New Features
pickfirst
LB policy (disabled by default) supports Happy Eyeballs, interleaving IPv4 and IPv6 address as described in RFC-8305 section 4, to attempt connections to multiple backends concurrently. The experimentalpickfirst
policy can be enabled by setting the environment variableGRPC_EXPERIMENTAL_ENABLE_NEW_PICK_FIRST
totrue
. (#7725, #7742)pick_first
load balancing policy (#7839)MethodHandler
, which is the type of an already-exported field inMethodDesc
(#7796)Bug Fixes
Behavior Changes
pick_first
LB policy to manage connections (#7826)API Changes
balancer.SubConn
interface to force implementors to embed a delegate implementation. This requirement is present in the interface documentation, but wasn't enforced earlier. (#7840)Performance Improvements
ReadAll()
method for more efficientio.Reader
consumption (#7653)Documentation
Configuration
📅 Schedule: Branch creation - "* 0-3 * * 1" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.