v1.0.0

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.

• Update protovalidate by @srikrsna-buf in #280

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

v1.0.0-rc.4

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

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

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

What's Changed

• Update to protovalidate v0.13.0 by @smaye81 in #256
• Validate MessageOneofRule by @srikrsna-buf in #257
• Fix error message for too many selected fields with required MessageOneofRule by @timostamm in #260
• Add implicit IGNORE_IF_UNPOPULATED for MessageOneofRule fields by @srikrsna-buf in #258

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

v0.13.1

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

What's Changed

• Validate MessageOneofRule by @srikrsna-buf in #257
• Fix error message for too many selected fields with required MessageOneofRule by @timostamm in #260
• Add implicit IGNORE_IF_UNPOPULATED for MessageOneofRule fields by @srikrsna-buf in #258

New Contributors

• @srikrsna-buf made their first contribution in #257

Full Changelog: v0.13.0...v0.13.1

v0.13.0

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

What's Changed

• Implement MessageOneof rule by @smaye81 in #254

Full Changelog: v1.0.0-rc.1...v0.13.0

v1.0.0-rc.2

This release is compatible with the v1.0.0-rc.2 release of Protovalidate.

What's Changed

• Implement MessageOneof rule by @smaye81 in #254

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

v1.0.0-rc.1

This release is compatible with the v1.0.0-rc.1 release of Protovalidate.

What's Changed

• Update to pv release candidate by @smaye81 in #252
• Flatten the resolve methods into the main package by @jchadwick-buf in #249
• Correctly validate WKT rules on incorrect field types by @smaye81 in #247

Full Changelog: v0.12.0...v1.0.0-rc.1

v0.12.0

Breaking Changes

The import path of protovalidate-go has recently changed! If you are updating from a version of protovalidate-go prior to v0.11.0, please update your source code to move the import path from github.com/bufbuild/protovalidate-go to buf.build/go/protovalidate.

This release makes the methods of the resolve package fallible, i.e. they now return an error. Also, we have removed support for the legacy protovalidate extension; this extension is quite old, predating protovalidate's addition to the protobuf extension registry, and thus we believe it is unlikely to be in use. However, if you are using binary descriptors that may be using fairly old versions of the protovalidate library, please ensure they are using protovalidate v0.2.0 or higher. Binary descriptors from earlier versions of the protovalidate library will be silently ignored, causing validation to always pass.

What's Changed

• Upgrade golangci-lint to latest by @pkwarren in #237
• Remove protoc-gen-validate dependency by @jchadwick-buf in #240
• Make resolve methods fallible by @jchadwick-buf in #241
• Enable staticcheck QF1006 linter by @pkwarren in #242
• Remove resolution of legacy protovalidate extension by @jchadwick-buf in #243

Full Changelog: v0.11.0...v0.12.0

v0.11.0

What's Changed

The import path of protovalidate-go has changed! Please update your source code to move the import path from github.com/bufbuild/protovalidate-go to buf.build/go/protovalidate.

• Rewrite import path to buf.build/go/protovalidate by @jchadwick-buf in #235

Full Changelog: v0.10.1...v0.11.0