Releases: bufbuild/protovalidate-es
v1.1.1
This release is compatible with the v1.1.0 release of Protovalidate.
What's Changed
Protovalidate CEL methods were previously also usable as functions due to a limitation in the CEL package. This release uses an updated version that is able to distinguish between methods and functions. This is inline with other Protovalidate implementations.
Full Changelog: v1.1.0...v1.1.1
v1.1.0
This release is compatible with the v1.1.0 release of Protovalidate.
What's Changed
- Fix Node 25 by @AdrienVannson in #103
- Use localName for StandardSchema validation error paths by @nakker1218 in #100
- Stop evaluation of field rules if the
requiredrule is violated by @timostamm in #108 - Raise an error for unregistered predefined rules by @timostamm in #106
- Make it so that you can define expression-only rules by @srikrsna-buf in #110
- Update protovalidate by @srikrsna-buf in #115
New Contributors
- @AdrienVannson made their first contribution in #103
- @nakker1218 made their first contribution in #100
Full Changelog: v1.0.0...v1.1.0
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 to protovalidate v1.0.0 by @timostamm in #86
Full Changelog: v0.8.0...v1.0.0
v1.0.0-rc.6
What's Changed
- Update
violation(s)ToPrototo also return the descriptor by @srikrsna-buf in #76
Full Changelog: v1.0.0-rc.5...v1.0.0-rc.6
v0.8.0
What's Changed
- Update
violation(s)ToPrototo also return the descriptor by @srikrsna-buf in #76
Full Changelog: v0.7.0...v0.8.0
v1.0.0-rc.5
What's Changed
Updated the CEL library version. This now passes most of the protovalidate conformance tests.
Full Changelog: v1.0.0-rc.4...v1.0.0-rc.5
v0.7.0
What's Changed
Updated the CEL library version. This now passes most of the protovalidate conformance tests.
Full Changelog: v0.6.0...v0.7.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_UNPOPULATEDis renamed toIGNORE_IF_ZERO_VALUE.
See bufbuild/protovalidate#397 for details.(buf.validate.message).disabledis removed.
You can replace it by addingIGNORE_ALWAYSto every field of the message. See bufbuild/protovalidate#394 for details.IGNORE_IF_DEFAULT_VALUEis removed.
In most cases, you can replace it withIGNORE_IF_ZERO_VALUE. See bufbuild/protovalidate#396 for details.
New Contributors
- @ichizero made their first contribution in #54
- @paul-sachs made their first contribution in #55
- @jrinehart-buf made their first contribution in #56
Full Changelog: v1.0.0-rc.3...v1.0.0-rc.4
v0.6.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_UNPOPULATEDis renamed toIGNORE_IF_ZERO_VALUE.
See bufbuild/protovalidate#397 for details.(buf.validate.message).disabledis removed.
You can replace it by addingIGNORE_ALWAYSto every field of the message. See bufbuild/protovalidate#394 for details.IGNORE_IF_DEFAULT_VALUEis removed.
In most cases, you can replace it withIGNORE_IF_ZERO_VALUE. See bufbuild/protovalidate#396 for details.
New Contributors
- @jrinehart-buf made their first contribution in #56
Full Changelog: v0.5.0...v0.6.0