Skip to content

Releases: bufbuild/protovalidate-go

v1.2.0

22 Apr 11:31
50eb290

Choose a tag to compare

This release is compatible with the v1.2.0 release of Protovalidate.

What's Changed

New Contributors

Full Changelog: v1.1.3...v1.2.0

v1.1.3

19 Feb 18:28
61167be

Choose a tag to compare

What's Changed

  • Fix a few godoc comments and update golangci-lint by @pkwarren in #306
  • Bump the go group across 1 directory with 2 updates by @dependabot[bot] in #308
  • Fix registry chain for pb.Map in NativeToValue by @rodaine in #309

Full Changelog: v1.1.2...v1.1.3

v1.1.2

11 Feb 21:54
e666f1a

Choose a tag to compare

What's Changed

  • Fix base type adapter missing builtin types by @rodaine in #305

Full Changelog: v1.1.1...v1.1.2

v1.1.1

10 Feb 10:29
3707b74

Choose a tag to compare

This release is compatible with the v1.1.0 release of Protovalidate.

What's Changed

  • Always provide all available variables by @srikrsna-buf in #297
  • Wrap protoreflect.Map with type information so we don't need to cast to map[any]any by @rodaine in #300
  • Avoid heap escape on kvPairs evaluation by @rodaine in #301
  • Implement registry chaining for CEL type isolation by @rodaine in #302

Full Changelog: v1.1.0...v1.1.1

v1.1.0

09 Dec 18:33
05e4c36

Choose a tag to compare

This release is compatible with the v1.1.0 release of Protovalidate.

What's Changed

Full Changelog: v1.0.1...v1.1.0

v1.0.1

18 Nov 20:59
15821df

Choose a tag to compare

What's Changed

Full Changelog: v1.0.0...v1.0.1

v1.0.0

12 Sep 16:24
927264e

Choose a tag to compare

Protovalidate is now v1.0

After two years of development, Protovalidate has reached v1.0, marking our commitment to stability and production readiness.
Read more in our blog post. Get started at https://protovalidate.com.

What's Changed

There are no functional changes compared to the previous release.

Full Changelog: v0.14.0...v1.0.0

v1.0.0-rc.4

17 Jul 18:02
80cf168

Choose a tag to compare

This release is compatible with the v0.14.0 release of Protovalidate.

Breaking changes

We want validation rules to be easy to understand for authors and consumers. To simplify Protovalidate, we are renaming an option and remove two others. This is a breaking change, and you will have to update your Protobuf files if they use the relevant options :

  • IGNORE_IF_UNPOPULATED is renamed to IGNORE_IF_ZERO_VALUE.
    See bufbuild/protovalidate#397 for details.
  • (buf.validate.message).disabled is removed.
    You can replace it by adding IGNORE_ALWAYS to every field of the message. See bufbuild/protovalidate#394 for details.
  • IGNORE_IF_DEFAULT_VALUE is removed.
    In most cases, you can replace it with IGNORE_IF_ZERO_VALUE. See bufbuild/protovalidate#396 for details.

Full Changelog: v1.0.0-rc.3...v1.0.0-rc.4

v0.14.0

17 Jul 17:41
80cf168

Choose a tag to compare

This release is compatible with the v0.14.0 release of Protovalidate.

Breaking changes

We want validation rules to be easy to understand for authors and consumers. To simplify Protovalidate, we are renaming an option and remove two others. This is a breaking change, and you will have to update your Protobuf files if they use the relevant options :

  • IGNORE_IF_UNPOPULATED is renamed to IGNORE_IF_ZERO_VALUE.
    See bufbuild/protovalidate#397 for details.
  • (buf.validate.message).disabled is removed.
    You can replace it by adding IGNORE_ALWAYS to every field of the message. See bufbuild/protovalidate#394 for details.
  • IGNORE_IF_DEFAULT_VALUE is removed.
    In most cases, you can replace it with IGNORE_IF_ZERO_VALUE. See bufbuild/protovalidate#396 for details.

Full Changelog: v0.13.1...v0.14.0

v1.0.0-rc.3

13 Jun 15:08
ce1a243

Choose a tag to compare

This release is compatible with the v0.13.3 release of Protovalidate.

What's Changed

Full Changelog: v1.0.0-rc.2...v1.0.0-rc.3