fix(deps): update module github.com/bufbuild/protovalidate-go to v0.8.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
github.com/bufbuild/protovalidate-go	v0.7.3 -> v0.8.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 protobuf buf.validate.Violations message alias, but a struct containing a slice of protovalidate.Violation instances. In most cases, accessing the Proto member of the violation is all that needs to be done:

     for _, violation := range err.Violations {
-        fmt.Println(violation.GetMessage())
+        fmt.Println(violation.Proto.GetMessage())
     }

protovalidate.ValidationError still has a ToProto() method that returns the protobuf buf.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: A protoreflect.Value containing the value of the field failing validation, if there is a field corresponding to the violation.
• FieldDescriptor: A protoreflect.FieldDescriptor corresponding to the field failing validation.
• RuleValue: A protoreflect.Value containing the value of the rule failing validation, if there is a rule corresponding to the violation.
• RuleDescriptor: A protoreflect.FieldDescriptor corresponding to the rule failing validation.

Take, for example, the following protobuf message schema:

message User {
    string email = 1 [(buf.validate.field).string.email = true];
}

If you try to validate the struct pb.User{Email: "invalid"}, the FieldValue will be "invalid" and the RuleValue will be true.

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 the FieldDescriptor will be nil.

What's Changed

• Implement structured field and rule paths, add field and rule values to ValidationErrors by @​jchadwick-buf in https://github.com/bufbuild/protovalidate-go/pull/154
• Bump the go group with 2 updates by @​dependabot in https://github.com/bufbuild/protovalidate-go/pull/161

Full Changelog: bufbuild/protovalidate-go@v0.7.3...v0.8.0

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 74.50%. Comparing base (24b77a6) to head (2f0f5f0).
Report is 1 commits behind head on 2.x.

Additional details and impacted files

@@           Coverage Diff           @@
##              2.x     #490   +/-   ##
=======================================
  Coverage   74.50%   74.50%           
=======================================
  Files         111      111           
  Lines        4323     4323           
=======================================
  Hits         3221     3221           
  Misses       1032     1032           
  Partials       70       70           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.