Bump build.buf:protovalidate from 0.2.1 to 0.9.1

[dependabot]

Bumps build.buf:protovalidate from 0.2.1 to 0.9.1.

Release notes

Sourced from build.buf:protovalidate's releases.

v0.9.1

What's Changed

This is a maintenance update that includes an important bug fix: in some situations, the CEL environment does not correctly get populated with its dependencies; specifically, when an expression refers to a submessage whose dependency is in a non-public import, it will not be added to the CEL environment.

• Update to protovalidate 0.12.0 by @​smaye81 in bufbuild/protovalidate-java#301
• Implement workaround for cel-java import issue by @​jchadwick-buf in bufbuild/protovalidate-java#302

Full Changelog: bufbuild/protovalidate-java@0.9.0...v0.9.1

v0.9.0

Breaking Changes

String formatting is now conformant with the CEL spec.

As a result, some formatting output may differ from previous versions. See #293, #294, and #295 for details on formatting changes.

What's Changed

• Fix overload declaration for format by @​smaye81 in bufbuild/protovalidate-java#295
• Add supplemental format conformance tests by @​smaye81 in bufbuild/protovalidate-java#294
• Add conformance testing to string.format implementation by @​smaye81 in bufbuild/protovalidate-java#293

Full Changelog: bufbuild/protovalidate-java@v0.8.0...v0.9.0

v0.8.0

Breaking Changes

New API for creating a validator.

Validators are now created via ValidatorFactory using a builder pattern. To migrate, users should make the following changes:

With no config

import build.buf.protovalidate.Validator;
+ import build.buf.protovalidate.ValidatorFactory;

Validator validator = new Validator();


Validator validator = ValidatorFactory.newBuilder().build();

With config

import build.buf.protovalidate.Validator;
+ import build.buf.protovalidate.ValidatorFactory;
Config cfg = Config.newBuilder().setFailFast(true).build();

Validator validator = new Validator(cfg);
</tr></table>

... (truncated)

Commits

• ed6392d Implement workaround for cel-java import issue (#302)
• 529a5c4 Update to protovalidate 0.12.0 (#301)
• 8342d2c Filter buf.gen.yaml files based on protoc version (#300)
• 53aa216 Update buf.gen.yaml versions for protobuf (#299)
• 8a1425d Bump org.junit:junit-bom from 5.12.2 to 5.13.0 (#296)
• c0bd4f8 Bump com.diffplug.spotless:spotless-plugin-gradle from 7.0.3 to 7.0.4 (#297)
• 976c284 Bump com.google.protobuf:protobuf-java from 4.31.0 to 4.31.1 (#298)
• b5d806e Fix overload declaration for format (#295)
• ce51220 Add supplemental format conformance tests (#294)
• 256eb5c Add conformance testing to string.format implementation (#293)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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 <dependency name> 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)

Summary by Sourcery

Build:

• Update protovalidate version in Maven pom to 0.9.1

[sourcery-ai]

Reviewer's Guide

This PR simply bumps the build.buf:protovalidate Java dependency from 0.2.1 to 0.9.1 in the Maven POM, pulling in the latest maintenance and breaking changes upstream.

Sequence Diagram for New protovalidate.Validator Instantiation

sequenceDiagram
  title: "Sequence Diagram for New protovalidate.Validator Instantiation"
  participant ClientCode
  participant ValidatorFactory
  participant Builder
  participant Validator

  ClientCode->>ValidatorFactory: newBuilder()
  ValidatorFactory-->>Builder: create & return builder instance
  activate Builder
  Builder-->>ClientCode: builder instance
  deactivate Builder

  alt With Configuration
    %% ClientCode obtains or has a 'config' instance of Config
    ClientCode->>Builder: setConfig(config)
    activate Builder
    Builder-->>ClientCode: self (builder instance)
    deactivate Builder
  end

  ClientCode->>Builder: build()
  activate Builder
  Builder->>Validator: create validator instance
  activate Validator
  Validator-->>Builder: validator instance
  deactivate Validator
  Builder-->>ClientCode: validator instance
  deactivate Builder

Loading

Class Diagram for protovalidate.Validator API Update

classDiagram
  title: "Class Diagram for protovalidate.Validator API Update"
  class ValidatorFactory {
    +static newBuilder() Builder
  }
  class Builder {
    +setConfig(Config) Builder
    +build() Validator
  }
  class Validator {
    %% Instantiation now via ValidatorFactory.Builder
    +validate(Message) ValidationResult
  }
  class Config {
    %% Configuration for Validator
  }
  ValidatorFactory ..> Builder : provides
  Builder ..> Config : uses
  Builder ..> Validator : creates

Loading

File-Level Changes

Change	Details	Files
Bump protovalidate dependency version	Changed tag from 0.2.1 to 0.9.1	pom.xml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[dependabot]

Superseded by #77.