@nebius/js-sdk 0.1.35 → 0.1.37

package/dist/esm/api/buf/validate/index.d.ts

@@ -3,192 +3,120 @@ import type { Dayjs, Duration, MessageFns, EnumInstance, EnumClass } from "../..
 import { customJson } from "../../../runtime/util/logging";
 import { FieldDescriptorProto_Type } from "../../google/protobuf";
 /**
- *  Specifies how FieldConstraints.ignore behaves. See the documentation for
- *  FieldConstraints.required for definitions of "populated" and "nullable".
+ *  Specifies how `FieldRules.ignore` behaves, depending on the field's value, and
+ *  whether the field tracks presence.
  *
  */
-export type Ignore = EnumInstance<"UNRECOGNIZED" | "IGNORE_UNSPECIFIED" | "IGNORE_IF_UNPOPULATED" | "IGNORE_IF_DEFAULT_VALUE" | "IGNORE_ALWAYS" | "IGNORE_EMPTY" | "IGNORE_DEFAULT">;
+export type Ignore = EnumInstance<"UNRECOGNIZED" | "IGNORE_UNSPECIFIED" | "IGNORE_IF_ZERO_VALUE" | "IGNORE_ALWAYS">;
 interface IgnoreValueMembers {
     /**
-     *  Validation is only skipped if it's an unpopulated nullable fields.
+     *  Ignore rules if the field tracks presence and is unset. This is the default
+     *  behavior.
+     *
+     *  In proto3, only message fields, members of a Protobuf `oneof`, and fields
+     *  with the `optional` label track presence. Consequently, the following fields
+     *  are always validated, whether a value is set or not:
      *
      *  ```proto
      *  syntax="proto3";
      *
-     *  message Request {
-     *    // The uri rule applies to any value, including the empty string.
-     *    string foo = 1 [
-     *      (buf.validate.field).string.uri = true
+     *  message RulesApply {
+     *    string email = 1 [
+     *      (buf.validate.field).string.email = true
      *    ];
-     *
-     *    // The uri rule only applies if the field is set, including if it's
-     *    // set to the empty string.
-     *    optional string bar = 2 [
-     *      (buf.validate.field).string.uri = true
+     *    int32 age = 2 [
+     *      (buf.validate.field).int32.gt = 0
      *    ];
-     *
-     *    // The min_items rule always applies, even if the list is empty.
-     *    repeated string baz = 3 [
-     *      (buf.validate.field).repeated.min_items = 3
-     *    ];
-     *
-     *    // The custom CEL rule applies only if the field is set, including if
-     *    // it's the "zero" value of that message.
-     *    SomeMessage quux = 4 [
-     *      (buf.validate.field).cel = {/* ... * /}
+     *    repeated string labels = 3 [
+     *      (buf.validate.field).repeated.min_items = 1
      *    ];
      *  }
      *  ```
      *
-     */
-    readonly IGNORE_UNSPECIFIED: EnumInstance<"UNRECOGNIZED" | "IGNORE_UNSPECIFIED" | "IGNORE_IF_UNPOPULATED" | "IGNORE_IF_DEFAULT_VALUE" | "IGNORE_ALWAYS" | "IGNORE_EMPTY" | "IGNORE_DEFAULT">;
-    /**
-     *  Validation is skipped if the field is unpopulated. This rule is redundant
-     *  if the field is already nullable. This value is equivalent behavior to the
-     *  deprecated ignore_empty rule.
+     *  In contrast, the following fields track presence, and are only validated if
+     *  a value is set:
      *
      *  ```proto
-     *  syntax="proto3
-     *
-     *  message Request {
-     *    // The uri rule applies only if the value is not the empty string.
-     *    string foo = 1 [
-     *      (buf.validate.field).string.uri = true,
-     *      (buf.validate.field).ignore = IGNORE_IF_UNPOPULATED
-     *    ];
-     *
-     *    // IGNORE_IF_UNPOPULATED is equivalent to IGNORE_UNSPECIFIED in this
-     *    // case: the uri rule only applies if the field is set, including if
-     *    // it's set to the empty string.
-     *    optional string bar = 2 [
-     *      (buf.validate.field).string.uri = true,
-     *      (buf.validate.field).ignore = IGNORE_IF_UNPOPULATED
-     *    ];
+     *  syntax="proto3";
      *
-     *    // The min_items rule only applies if the list has at least one item.
-     *    repeated string baz = 3 [
-     *      (buf.validate.field).repeated.min_items = 3,
-     *      (buf.validate.field).ignore = IGNORE_IF_UNPOPULATED
+     *  message RulesApplyIfSet {
+     *    optional string email = 1 [
+     *      (buf.validate.field).string.email = true
      *    ];
-     *
-     *    // IGNORE_IF_UNPOPULATED is equivalent to IGNORE_UNSPECIFIED in this
-     *    // case: the custom CEL rule applies only if the field is set, including
-     *    // if it's the "zero" value of that message.
-     *    SomeMessage quux = 4 [
-     *      (buf.validate.field).cel = {/* ... * /},
-     *      (buf.validate.field).ignore = IGNORE_IF_UNPOPULATED
+     *    oneof ref {
+     *      string reference = 2 [
+     *        (buf.validate.field).string.uuid = true
+     *      ];
+     *      string name = 3 [
+     *        (buf.validate.field).string.min_len = 4
+     *      ];
+     *    }
+     *    SomeMessage msg = 4 [
+     *      (buf.validate.field).cel = {/* ... * /}
      *    ];
      *  }
      *  ```
      *
-     */
-    readonly IGNORE_IF_UNPOPULATED: EnumInstance<"UNRECOGNIZED" | "IGNORE_UNSPECIFIED" | "IGNORE_IF_UNPOPULATED" | "IGNORE_IF_DEFAULT_VALUE" | "IGNORE_ALWAYS" | "IGNORE_EMPTY" | "IGNORE_DEFAULT">;
-    /**
-     *  Validation is skipped if the field is unpopulated or if it is a nullable
-     *  field populated with its default value. This is typically the zero or
-     *  empty value, but proto2 scalars support custom defaults. For messages, the
-     *  default is a non-null message with all its fields unpopulated.
+     *  To ensure that such a field is set, add the `required` rule.
      *
-     *  ```proto
-     *  syntax="proto3
+     *  To learn which fields track presence, see the
+     *  [Field Presence cheat sheet](https://protobuf.dev/programming-guides/field_presence/#cheat).
      *
-     *  message Request {
-     *    // IGNORE_IF_DEFAULT_VALUE is equivalent to IGNORE_IF_UNPOPULATED in
-     *    // this case; the uri rule applies only if the value is not the empty
-     *    // string.
-     *    string foo = 1 [
-     *      (buf.validate.field).string.uri = true,
-     *      (buf.validate.field).ignore = IGNORE_IF_DEFAULT_VALUE
-     *    ];
-     *
-     *    // The uri rule only applies if the field is set to a value other than
-     *    // the empty string.
-     *    optional string bar = 2 [
-     *      (buf.validate.field).string.uri = true,
-     *      (buf.validate.field).ignore = IGNORE_IF_DEFAULT_VALUE
-     *    ];
-     *
-     *    // IGNORE_IF_DEFAULT_VALUE is equivalent to IGNORE_IF_UNPOPULATED in
-     *    // this case; the min_items rule only applies if the list has at least
-     *    // one item.
-     *    repeated string baz = 3 [
-     *      (buf.validate.field).repeated.min_items = 3,
-     *      (buf.validate.field).ignore = IGNORE_IF_DEFAULT_VALUE
-     *    ];
-     *
-     *    // The custom CEL rule only applies if the field is set to a value other
-     *    // than an empty message (i.e., fields are unpopulated).
-     *    SomeMessage quux = 4 [
-     *      (buf.validate.field).cel = {/* ... * /},
-     *      (buf.validate.field).ignore = IGNORE_IF_DEFAULT_VALUE
-     *    ];
-     *  }
-     *  ```
+     */
+    readonly IGNORE_UNSPECIFIED: EnumInstance<"UNRECOGNIZED" | "IGNORE_UNSPECIFIED" | "IGNORE_IF_ZERO_VALUE" | "IGNORE_ALWAYS">;
+    /**
+     *  Ignore rules if the field is unset, or set to the zero value.
      *
-     *  This rule is affected by proto2 custom default values:
+     *  The zero value depends on the field type:
+     *  - For strings, the zero value is the empty string.
+     *  - For bytes, the zero value is empty bytes.
+     *  - For bool, the zero value is false.
+     *  - For numeric types, the zero value is zero.
+     *  - For enums, the zero value is the first defined enum value.
+     *  - For repeated fields, the zero is an empty list.
+     *  - For map fields, the zero is an empty map.
+     *  - For message fields, absence of the message (typically a null-value) is considered zero value.
      *
-     *  ```proto
-     *  syntax="proto2";
-     *
-     *  message Request {
-     *    // The gt rule only applies if the field is set and it's value is not
-     *    the default (i.e., not -42). The rule even applies if the field is set
-     *    to zero since the default value differs.
-     *    optional int32 value = 1 [
-     *      default = -42,
-     *      (buf.validate.field).int32.gt = 0,
-     *      (buf.validate.field).ignore = IGNORE_IF_DEFAULT_VALUE
-     *    ];
-     *  }
+     *  For fields that track presence (e.g. adding the `optional` label in proto3),
+     *  this a no-op and behavior is the same as the default `IGNORE_UNSPECIFIED`.
      *
      */
-    readonly IGNORE_IF_DEFAULT_VALUE: EnumInstance<"UNRECOGNIZED" | "IGNORE_UNSPECIFIED" | "IGNORE_IF_UNPOPULATED" | "IGNORE_IF_DEFAULT_VALUE" | "IGNORE_ALWAYS" | "IGNORE_EMPTY" | "IGNORE_DEFAULT">;
+    readonly IGNORE_IF_ZERO_VALUE: EnumInstance<"UNRECOGNIZED" | "IGNORE_UNSPECIFIED" | "IGNORE_IF_ZERO_VALUE" | "IGNORE_ALWAYS">;
     /**
-     *  The validation rules of this field will be skipped and not evaluated. This
-     *  is useful for situations that necessitate turning off the rules of a field
-     *  containing a message that may not make sense in the current context, or to
-     *  temporarily disable constraints during development.
+     *  Always ignore rules, including the `required` rule.
+     *
+     *  This is useful for ignoring the rules of a referenced message, or to
+     *  temporarily ignore rules during development.
      *
      *  ```proto
      *  message MyMessage {
-     *    // The field's rules will always be ignored, including any validation's
+     *    // The field's rules will always be ignored, including any validations
      *    // on value's fields.
      *    MyOtherMessage value = 1 [
-     *      (buf.validate.field).ignore = IGNORE_ALWAYS];
+     *      (buf.validate.field).ignore = IGNORE_ALWAYS
+     *    ];
      *  }
      *  ```
      *
      */
-    readonly IGNORE_ALWAYS: EnumInstance<"UNRECOGNIZED" | "IGNORE_UNSPECIFIED" | "IGNORE_IF_UNPOPULATED" | "IGNORE_IF_DEFAULT_VALUE" | "IGNORE_ALWAYS" | "IGNORE_EMPTY" | "IGNORE_DEFAULT">;
-    /**
-     *  Deprecated: Use IGNORE_IF_UNPOPULATED instead. TODO: Remove this value pre-v1.
-     *
-     * @deprecated Deprecated.
-     */
-    readonly IGNORE_EMPTY: EnumInstance<"UNRECOGNIZED" | "IGNORE_UNSPECIFIED" | "IGNORE_IF_UNPOPULATED" | "IGNORE_IF_DEFAULT_VALUE" | "IGNORE_ALWAYS" | "IGNORE_EMPTY" | "IGNORE_DEFAULT">;
-    /**
-     *  Deprecated: Use IGNORE_IF_DEFAULT_VALUE. TODO: Remove this value pre-v1.
-     *
-     * @deprecated Deprecated.
-     */
-    readonly IGNORE_DEFAULT: EnumInstance<"UNRECOGNIZED" | "IGNORE_UNSPECIFIED" | "IGNORE_IF_UNPOPULATED" | "IGNORE_IF_DEFAULT_VALUE" | "IGNORE_ALWAYS" | "IGNORE_EMPTY" | "IGNORE_DEFAULT">;
+    readonly IGNORE_ALWAYS: EnumInstance<"UNRECOGNIZED" | "IGNORE_UNSPECIFIED" | "IGNORE_IF_ZERO_VALUE" | "IGNORE_ALWAYS">;
 }
-export type IgnoreClass = EnumClass<"UNRECOGNIZED" | "IGNORE_UNSPECIFIED" | "IGNORE_IF_UNPOPULATED" | "IGNORE_IF_DEFAULT_VALUE" | "IGNORE_ALWAYS" | "IGNORE_EMPTY" | "IGNORE_DEFAULT"> & IgnoreValueMembers;
+export type IgnoreClass = EnumClass<"UNRECOGNIZED" | "IGNORE_UNSPECIFIED" | "IGNORE_IF_ZERO_VALUE" | "IGNORE_ALWAYS"> & IgnoreValueMembers;
 export declare const Ignore: IgnoreClass;
 /**
- *  WellKnownRegex contain some well-known patterns.
+ *  KnownRegex contains some well-known patterns.
  *
  */
 export type KnownRegex = EnumInstance<"UNRECOGNIZED" | "KNOWN_REGEX_UNSPECIFIED" | "KNOWN_REGEX_HTTP_HEADER_NAME" | "KNOWN_REGEX_HTTP_HEADER_VALUE">;
 interface KnownRegexValueMembers {
     readonly KNOWN_REGEX_UNSPECIFIED: EnumInstance<"UNRECOGNIZED" | "KNOWN_REGEX_UNSPECIFIED" | "KNOWN_REGEX_HTTP_HEADER_NAME" | "KNOWN_REGEX_HTTP_HEADER_VALUE">;
     /**
-     *  HTTP header name as defined by [RFC 7230](https://tools.ietf.org/html/rfc7230#section-3.2).
+     *  HTTP header name as defined by [RFC 7230](https://datatracker.ietf.org/doc/html/rfc7230#section-3.2).
      *
      */
     readonly KNOWN_REGEX_HTTP_HEADER_NAME: EnumInstance<"UNRECOGNIZED" | "KNOWN_REGEX_UNSPECIFIED" | "KNOWN_REGEX_HTTP_HEADER_NAME" | "KNOWN_REGEX_HTTP_HEADER_VALUE">;
     /**
-     *  HTTP header value as defined by [RFC 7230](https://tools.ietf.org/html/rfc7230#section-3.2.4).
+     *  HTTP header value as defined by [RFC 7230](https://datatracker.ietf.org/doc/html/rfc7230#section-3.2.4).
      *
      */
     readonly KNOWN_REGEX_HTTP_HEADER_VALUE: EnumInstance<"UNRECOGNIZED" | "KNOWN_REGEX_UNSPECIFIED" | "KNOWN_REGEX_HTTP_HEADER_NAME" | "KNOWN_REGEX_HTTP_HEADER_VALUE">;
@@ -196,10 +124,10 @@ interface KnownRegexValueMembers {
 export type KnownRegexClass = EnumClass<"UNRECOGNIZED" | "KNOWN_REGEX_UNSPECIFIED" | "KNOWN_REGEX_HTTP_HEADER_NAME" | "KNOWN_REGEX_HTTP_HEADER_VALUE"> & KnownRegexValueMembers;
 export declare const KnownRegex: KnownRegexClass;
 /**
- *  `Constraint` represents a validation rule written in the Common Expression
- *  Language (CEL) syntax. Each Constraint includes a unique identifier, an
+ *  `Rule` represents a validation rule written in the Common Expression
+ *  Language (CEL) syntax. Each Rule includes a unique identifier, an
  *  optional error message, and the CEL expression to evaluate. For more
- *  information on CEL, [see our documentation](https://github.com/bufbuild/protovalidate/blob/main/docs/cel.md).
+ *  information, [see our documentation](https://buf.build/docs/protovalidate/schemas/custom-rules/).
  *
  *  ```proto
  *  message Foo {
@@ -213,19 +141,19 @@ export declare const KnownRegex: KnownRegexClass;
  *  ```
  *
  */
-export interface Constraint {
-    $type: "buf.validate.Constraint";
+export interface Rule {
+    $type: "buf.validate.Rule";
     [unknownFieldsSymbol]?: Uint8Array | undefined;
     [customJson]?: () => unknown;
     /**
-     *  `id` is a string that serves as a machine-readable name for this Constraint.
+     *  `id` is a string that serves as a machine-readable name for this Rule.
      *  It should be unique within its scope, which could be either a message or a field.
      *
      */
     id?: string | undefined;
     /**
      *  `message` is an optional field that provides a human-readable error message
-     *  for this Constraint when the CEL expression evaluates to false. If a
+     *  for this Rule when the CEL expression evaluates to false. If a
      *  non-empty message is provided, any strings resulting from the CEL
      *  expression evaluation are ignored.
      *
@@ -240,33 +168,42 @@ export interface Constraint {
      */
     expression?: string | undefined;
 }
-export declare const Constraint: MessageFns<Constraint, "buf.validate.Constraint">;
+export declare const Rule: MessageFns<Rule, "buf.validate.Rule">;
 /**
- *  MessageConstraints represents validation rules that are applied to the entire message.
- *  It includes disabling options and a list of Constraint messages representing Common Expression Language (CEL) validation rules.
+ *  MessageRules represents validation rules that are applied to the entire message.
+ *  It includes disabling options and a list of Rule messages representing Common Expression Language (CEL) validation rules.
  *
  */
-export interface MessageConstraints {
-    $type: "buf.validate.MessageConstraints";
+export interface MessageRules {
+    $type: "buf.validate.MessageRules";
     [unknownFieldsSymbol]?: Uint8Array | undefined;
     [customJson]?: () => unknown;
     /**
-     *  `disabled` is a boolean flag that, when set to true, nullifies any validation rules for this message.
-     *  This includes any fields within the message that would otherwise support validation.
+     *  `cel_expression` is a repeated field CEL expressions. Each expression specifies a validation
+     *  rule to be applied to this message. These rules are written in Common Expression Language (CEL) syntax.
+     *
+     *  This is a simplified form of the `cel` Rule field, where only `expression` is set. This allows for
+     *  simpler syntax when defining CEL Rules where `id` and `message` derived from the `expression`. `id` will
+     *  be same as the `expression`.
+     *
+     *  For more information, [see our documentation](https://buf.build/docs/protovalidate/schemas/custom-rules/).
      *
      *  ```proto
      *  message MyMessage {
-     *    // validation will be bypassed for this message
-     *    option (buf.validate.message).disabled = true;
+     *    // The field `foo` must be greater than 42.
+     *    option (buf.validate.message).cel_expression = "this.foo > 42";
+     *    // The field `foo` must be less than 84.
+     *    option (buf.validate.message).cel_expression = "this.foo < 84";
+     *    optional int32 foo = 1;
      *  }
      *  ```
      *
      */
-    disabled?: boolean | undefined;
+    celExpression: string[];
     /**
-     *  `cel` is a repeated field of type Constraint. Each Constraint specifies a validation rule to be applied to this message.
-     *  These constraints are written in Common Expression Language (CEL) syntax. For more information on
-     *  CEL, [see our documentation](https://github.com/bufbuild/protovalidate/blob/main/docs/cel.md).
+     *  `cel` is a repeated field of type Rule. Each Rule specifies a validation rule to be applied to this message.
+     *  These rules are written in Common Expression Language (CEL) syntax. For more information,
+     *  [see our documentation](https://buf.build/docs/protovalidate/schemas/custom-rules/).
      *
      *
      *  ```proto
@@ -282,22 +219,77 @@ export interface MessageConstraints {
      *  ```
      *
      */
-    cel: Constraint[];
+    cel: Rule[];
+    /**
+     *  `oneof` is a repeated field of type MessageOneofRule that specifies a list of fields
+     *  of which at most one can be present. If `required` is also specified, then exactly one
+     *  of the specified fields _must_ be present.
+     *
+     *  This will enforce oneof-like constraints with a few features not provided by
+     *  actual Protobuf oneof declarations:
+     *    1. Repeated and map fields are allowed in this validation. In a Protobuf oneof,
+     *       only scalar fields are allowed.
+     *    2. Fields with implicit presence are allowed. In a Protobuf oneof, all member
+     *       fields have explicit presence. This means that, for the purpose of determining
+     *       how many fields are set, explicitly setting such a field to its zero value is
+     *       effectively the same as not setting it at all.
+     *    3. This will always generate validation errors for a message unmarshalled from
+     *       serialized data that sets more than one field. With a Protobuf oneof, when
+     *       multiple fields are present in the serialized form, earlier values are usually
+     *       silently ignored when unmarshalling, with only the last field being set when
+     *       unmarshalling completes.
+     *
+     *  Note that adding a field to a `oneof` will also set the IGNORE_IF_ZERO_VALUE on the fields. This means
+     *  only the field that is set will be validated and the unset fields are not validated according to the field rules.
+     *  This behavior can be overridden by setting `ignore` against a field.
+     *
+     *  ```proto
+     *  message MyMessage {
+     *    // Only one of `field1` or `field2` _can_ be present in this message.
+     *    option (buf.validate.message).oneof = { fields: ["field1", "field2"] };
+     *    // Exactly one of `field3` or `field4` _must_ be present in this message.
+     *    option (buf.validate.message).oneof = { fields: ["field3", "field4"], required: true };
+     *    string field1 = 1;
+     *    bytes field2 = 2;
+     *    bool field3 = 3;
+     *    int32 field4 = 4;
+     *  }
+     *  ```
+     *
+     */
+    oneof: MessageOneofRule[];
 }
-export declare const MessageConstraints: MessageFns<MessageConstraints, "buf.validate.MessageConstraints">;
+export declare const MessageRules: MessageFns<MessageRules, "buf.validate.MessageRules">;
+export interface MessageOneofRule {
+    $type: "buf.validate.MessageOneofRule";
+    [unknownFieldsSymbol]?: Uint8Array | undefined;
+    [customJson]?: () => unknown;
+    /**
+     *  A list of field names to include in the oneof. All field names must be
+     *  defined in the message. At least one field must be specified, and
+     *  duplicates are not permitted.
+     *
+     */
+    fields: string[];
+    /**
+     *  If true, one of the fields specified _must_ be set.
+     *
+     */
+    required?: boolean | undefined;
+}
+export declare const MessageOneofRule: MessageFns<MessageOneofRule, "buf.validate.MessageOneofRule">;
 /**
- *  The `OneofConstraints` message type enables you to manage constraints for
+ *  The `OneofRules` message type enables you to manage rules for
  *  oneof fields in your protobuf messages.
  *
  */
-export interface OneofConstraints {
-    $type: "buf.validate.OneofConstraints";
+export interface OneofRules {
+    $type: "buf.validate.OneofRules";
     [unknownFieldsSymbol]?: Uint8Array | undefined;
     [customJson]?: () => unknown;
     /**
-     *  If `required` is true, exactly one field of the oneof must be present. A
-     *  validation error is returned if no fields in the oneof are present. The
-     *  field itself may still be a default value; further constraints
+     *  If `required` is true, exactly one field of the oneof must be set. A
+     *  validation error is returned if no fields in the oneof are set. Further rules
      *  should be placed on the fields themselves to ensure they are valid values,
      *  such as `min_len` or `gt`.
      *
@@ -316,20 +308,39 @@ export interface OneofConstraints {
      */
     required?: boolean | undefined;
 }
-export declare const OneofConstraints: MessageFns<OneofConstraints, "buf.validate.OneofConstraints">;
+export declare const OneofRules: MessageFns<OneofRules, "buf.validate.OneofRules">;
 /**
- *  FieldConstraints encapsulates the rules for each type of field. Depending on
+ *  FieldRules encapsulates the rules for each type of field. Depending on
  *  the field, the correct set should be used to ensure proper validations.
  *
  */
-export interface FieldConstraints {
-    $type: "buf.validate.FieldConstraints";
+export interface FieldRules {
+    $type: "buf.validate.FieldRules";
     [unknownFieldsSymbol]?: Uint8Array | undefined;
     [customJson]?: () => unknown;
+    /**
+     *  `cel_expression` is a repeated field CEL expressions. Each expression specifies a validation
+     *  rule to be applied to this message. These rules are written in Common Expression Language (CEL) syntax.
+     *
+     *  This is a simplified form of the `cel` Rule field, where only `expression` is set. This allows for
+     *  simpler syntax when defining CEL Rules where `id` and `message` derived from the `expression`. `id` will
+     *  be same as the `expression`.
+     *
+     *  For more information, [see our documentation](https://buf.build/docs/protovalidate/schemas/custom-rules/).
+     *
+     *  ```proto
+     *  message MyMessage {
+     *    // The field `value` must be greater than 42.
+     *    optional int32 value = 1 [(buf.validate.field).cel_expression = "this > 42"];
+     *  }
+     *  ```
+     *
+     */
+    celExpression: string[];
     /**
      *  `cel` is a repeated field used to represent a textual expression
-     *  in the Common Expression Language (CEL) syntax. For more information on
-     *  CEL, [see our documentation](https://github.com/bufbuild/protovalidate/blob/main/docs/cel.md).
+     *  in the Common Expression Language (CEL) syntax. For more information,
+     *  [see our documentation](https://buf.build/docs/protovalidate/schemas/custom-rules/).
      *
      *  ```proto
      *  message MyMessage {
@@ -343,57 +354,83 @@ export interface FieldConstraints {
      *  ```
      *
      */
-    cel: Constraint[];
+    cel: Rule[];
     /**
-     *  If `required` is true, the field must be populated. A populated field can be
-     *  described as "serialized in the wire format," which includes:
+     *  If `required` is true, the field must be set. A validation error is returned
+     *  if the field is not set.
      *
-     *  - the following "nullable" fields must be explicitly set to be considered populated:
-     *    - singular message fields (whose fields may be unpopulated/default values)
-     *    - member fields of a oneof (may be their default value)
-     *    - proto3 optional fields (may be their default value)
-     *    - proto2 scalar fields (both optional and required)
-     *  - proto3 scalar fields must be non-zero to be considered populated
-     *  - repeated and map fields must be non-empty to be considered populated
+     *  ```proto
+     *  syntax="proto3";
+     *
+     *  message FieldsWithPresence {
+     *    // Requires any string to be set, including the empty string.
+     *    optional string link = 1 [
+     *      (buf.validate.field).required = true
+     *    ];
+     *    // Requires true or false to be set.
+     *    optional bool disabled = 2 [
+     *      (buf.validate.field).required = true
+     *    ];
+     *    // Requires a message to be set, including the empty message.
+     *    SomeMessage msg = 4 [
+     *      (buf.validate.field).required = true
+     *    ];
+     *  }
+     *  ```
+     *
+     *  All fields in the example above track presence. By default, Protovalidate
+     *  ignores rules on those fields if no value is set. `required` ensures that
+     *  the fields are set and valid.
+     *
+     *  Fields that don't track presence are always validated by Protovalidate,
+     *  whether they are set or not. It is not necessary to add `required`. It
+     *  can be added to indicate that the field cannot be the zero value.
      *
      *  ```proto
-     *  message MyMessage {
-     *    // The field `value` must be set to a non-null value.
-     *    optional MyOtherMessage value = 1 [(buf.validate.field).required = true];
+     *  syntax="proto3";
+     *
+     *  message FieldsWithoutPresence {
+     *    // `string.email` always applies, even to an empty string.
+     *    string link = 1 [
+     *      (buf.validate.field).string.email = true
+     *    ];
+     *    // `repeated.min_items` always applies, even to an empty list.
+     *    repeated string labels = 2 [
+     *      (buf.validate.field).repeated.min_items = 1
+     *    ];
+     *    // `required`, for fields that don't track presence, indicates
+     *    // the value of the field can't be the zero value.
+     *    int32 zero_value_not_allowed = 3 [
+     *      (buf.validate.field).required = true
+     *    ];
      *  }
      *  ```
      *
+     *  To learn which fields track presence, see the
+     *  [Field Presence cheat sheet](https://protobuf.dev/programming-guides/field_presence/#cheat).
+     *
+     *  Note: While field rules can be applied to repeated items, map keys, and map
+     *  values, the elements are always considered to be set. Consequently,
+     *  specifying `repeated.items.required` is redundant.
+     *
      */
     required?: boolean | undefined;
     /**
-     *  Skip validation on the field if its value matches the specified criteria.
-     *  See Ignore enum for details.
+     *  Ignore validation rules on the field if its value matches the specified
+     *  criteria. See the `Ignore` enum for details.
      *
      *  ```proto
      *  message UpdateRequest {
-     *    // The uri rule only applies if the field is populated and not an empty
-     *    // string.
-     *    optional string url = 1 [
-     *      (buf.validate.field).ignore = IGNORE_IF_DEFAULT_VALUE,
-     *      (buf.validate.field).string.uri = true,
+     *    // The uri rule only applies if the field is not an empty string.
+     *    string url = 1 [
+     *      (buf.validate.field).ignore = IGNORE_IF_ZERO_VALUE,
+     *      (buf.validate.field).string.uri = true
      *    ];
      *  }
      *  ```
      *
      */
     ignore?: Ignore | undefined;
-    /**
-     *  DEPRECATED: use ignore=IGNORE_ALWAYS instead. TODO: remove this field pre-v1.
-     *
-     * @deprecated Deprecated.
-     */
-    skipped?: boolean | undefined;
-    /**
-     *  DEPRECATED: use ignore=IGNORE_IF_UNPOPULATED instead. TODO: remove this field pre-v1.
-     *
-     * @deprecated Deprecated.
-     */
-    ignoreEmpty?: boolean | undefined;
     type?: {
         $case: "float";
         float: FloatRules;
@@ -454,25 +491,28 @@ export interface FieldConstraints {
     } | {
         $case: "duration";
         duration: DurationRules;
+    } | {
+        $case: "fieldMask";
+        fieldMask: FieldMaskRules;
     } | {
         $case: "timestamp";
         timestamp: TimestampRules;
     } | undefined;
 }
-export declare const FieldConstraints: MessageFns<FieldConstraints, "buf.validate.FieldConstraints">;
+export declare const FieldRules: MessageFns<FieldRules, "buf.validate.FieldRules">;
 /**
- *  PredefinedConstraints are custom constraints that can be re-used with
+ *  PredefinedRules are custom rules that can be re-used with
  *  multiple fields.
  *
  */
-export interface PredefinedConstraints {
-    $type: "buf.validate.PredefinedConstraints";
+export interface PredefinedRules {
+    $type: "buf.validate.PredefinedRules";
     [unknownFieldsSymbol]?: Uint8Array | undefined;
     [customJson]?: () => unknown;
     /**
      *  `cel` is a repeated field used to represent a textual expression
-     *  in the Common Expression Language (CEL) syntax. For more information on
-     *  CEL, [see our documentation](https://github.com/bufbuild/protovalidate/blob/main/docs/cel.md).
+     *  in the Common Expression Language (CEL) syntax. For more information,
+     *  [see our documentation](https://buf.build/docs/protovalidate/schemas/predefined-rules/).
      *
      *  ```proto
      *  message MyMessage {
@@ -486,11 +526,11 @@ export interface PredefinedConstraints {
      *  ```
      *
      */
-    cel: Constraint[];
+    cel: Rule[];
 }
-export declare const PredefinedConstraints: MessageFns<PredefinedConstraints, "buf.validate.PredefinedConstraints">;
+export declare const PredefinedRules: MessageFns<PredefinedRules, "buf.validate.PredefinedRules">;
 /**
- *  FloatRules describes the constraints applied to `float` values. These
+ *  FloatRules describes the rules applied to `float` values. These
  *  rules may also be applied to the `google.protobuf.FloatValue` Well-Known-Type.
  *
  */
@@ -519,7 +559,7 @@ export interface FloatRules {
      *  ```proto
      *  message MyFloat {
      *    // value must be in list [1.0, 2.0, 3.0]
-     *    repeated float value = 1 (buf.validate.field).float = { in: [1.0, 2.0, 3.0] };
+     *    float value = 1 [(buf.validate.field).float = { in: [1.0, 2.0, 3.0] }];
      *  }
      *  ```
      *
@@ -533,7 +573,7 @@ export interface FloatRules {
      *  ```proto
      *  message MyFloat {
      *    // value must not be in list [1.0, 2.0, 3.0]
-     *    repeated float value = 1 (buf.validate.field).float = { not_in: [1.0, 2.0, 3.0] };
+     *    float value = 1 [(buf.validate.field).float = { not_in: [1.0, 2.0, 3.0] }];
      *  }
      *  ```
      *
@@ -547,14 +587,14 @@ export interface FloatRules {
     finite?: boolean | undefined;
     /**
      *  `example` specifies values that the field may have. These values SHOULD
-     *  conform to other constraints. `example` values will not impact validation
+     *  conform to other rules. `example` values will not impact validation
      *  but may be used as helpful guidance on how to populate the given field.
      *
      *  ```proto
      *  message MyFloat {
      *    float value = 1 [
      *      (buf.validate.field).float.example = 1.0,
-     *      (buf.validate.field).float.example = "Infinity"
+     *      (buf.validate.field).float.example = inf
      *    ];
      *  }
      *  ```
@@ -578,7 +618,7 @@ export interface FloatRules {
 }
 export declare const FloatRules: MessageFns<FloatRules, "buf.validate.FloatRules">;
 /**
- *  DoubleRules describes the constraints applied to `double` values. These
+ *  DoubleRules describes the rules applied to `double` values. These
  *  rules may also be applied to the `google.protobuf.DoubleValue` Well-Known-Type.
  *
  */
@@ -607,7 +647,7 @@ export interface DoubleRules {
      *  ```proto
      *  message MyDouble {
      *    // value must be in list [1.0, 2.0, 3.0]
-     *    repeated double value = 1 (buf.validate.field).double = { in: [1.0, 2.0, 3.0] };
+     *    double value = 1 [(buf.validate.field).double = { in: [1.0, 2.0, 3.0] }];
      *  }
      *  ```
      *
@@ -621,7 +661,7 @@ export interface DoubleRules {
      *  ```proto
      *  message MyDouble {
      *    // value must not be in list [1.0, 2.0, 3.0]
-     *    repeated double value = 1 (buf.validate.field).double = { not_in: [1.0, 2.0, 3.0] };
+     *    double value = 1 [(buf.validate.field).double = { not_in: [1.0, 2.0, 3.0] }];
      *  }
      *  ```
      *
@@ -635,14 +675,14 @@ export interface DoubleRules {
     finite?: boolean | undefined;
     /**
      *  `example` specifies values that the field may have. These values SHOULD
-     *  conform to other constraints. `example` values will not impact validation
+     *  conform to other rules. `example` values will not impact validation
      *  but may be used as helpful guidance on how to populate the given field.
      *
      *  ```proto
      *  message MyDouble {
      *    double value = 1 [
      *      (buf.validate.field).double.example = 1.0,
-     *      (buf.validate.field).double.example = "Infinity"
+     *      (buf.validate.field).double.example = inf
      *    ];
      *  }
      *  ```
@@ -666,7 +706,7 @@ export interface DoubleRules {
 }
 export declare const DoubleRules: MessageFns<DoubleRules, "buf.validate.DoubleRules">;
 /**
- *  Int32Rules describes the constraints applied to `int32` values. These
+ *  Int32Rules describes the rules applied to `int32` values. These
  *  rules may also be applied to the `google.protobuf.Int32Value` Well-Known-Type.
  *
  */
@@ -695,7 +735,7 @@ export interface Int32Rules {
      *  ```proto
      *  message MyInt32 {
      *    // value must be in list [1, 2, 3]
-     *    repeated int32 value = 1 (buf.validate.field).int32 = { in: [1, 2, 3] };
+     *    int32 value = 1 [(buf.validate.field).int32 = { in: [1, 2, 3] }];
      *  }
      *  ```
      *
@@ -709,7 +749,7 @@ export interface Int32Rules {
      *  ```proto
      *  message MyInt32 {
      *    // value must not be in list [1, 2, 3]
-     *    repeated int32 value = 1 (buf.validate.field).int32 = { not_in: [1, 2, 3] };
+     *    int32 value = 1 [(buf.validate.field).int32 = { not_in: [1, 2, 3] }];
      *  }
      *  ```
      *
@@ -717,7 +757,7 @@ export interface Int32Rules {
     notIn: number[];
     /**
      *  `example` specifies values that the field may have. These values SHOULD
-     *  conform to other constraints. `example` values will not impact validation
+     *  conform to other rules. `example` values will not impact validation
      *  but may be used as helpful guidance on how to populate the given field.
      *
      *  ```proto
@@ -748,7 +788,7 @@ export interface Int32Rules {
 }
 export declare const Int32Rules: MessageFns<Int32Rules, "buf.validate.Int32Rules">;
 /**
- *  Int64Rules describes the constraints applied to `int64` values. These
+ *  Int64Rules describes the rules applied to `int64` values. These
  *  rules may also be applied to the `google.protobuf.Int64Value` Well-Known-Type.
  *
  */
@@ -777,7 +817,7 @@ export interface Int64Rules {
      *  ```proto
      *  message MyInt64 {
      *    // value must be in list [1, 2, 3]
-     *    repeated int64 value = 1 (buf.validate.field).int64 = { in: [1, 2, 3] };
+     *    int64 value = 1 [(buf.validate.field).int64 = { in: [1, 2, 3] }];
      *  }
      *  ```
      *
@@ -791,7 +831,7 @@ export interface Int64Rules {
      *  ```proto
      *  message MyInt64 {
      *    // value must not be in list [1, 2, 3]
-     *    repeated int64 value = 1 (buf.validate.field).int64 = { not_in: [1, 2, 3] };
+     *    int64 value = 1 [(buf.validate.field).int64 = { not_in: [1, 2, 3] }];
      *  }
      *  ```
      *
@@ -799,7 +839,7 @@ export interface Int64Rules {
     notIn: Long[];
     /**
      *  `example` specifies values that the field may have. These values SHOULD
-     *  conform to other constraints. `example` values will not impact validation
+     *  conform to other rules. `example` values will not impact validation
      *  but may be used as helpful guidance on how to populate the given field.
      *
      *  ```proto
@@ -830,7 +870,7 @@ export interface Int64Rules {
 }
 export declare const Int64Rules: MessageFns<Int64Rules, "buf.validate.Int64Rules">;
 /**
- *  UInt32Rules describes the constraints applied to `uint32` values. These
+ *  UInt32Rules describes the rules applied to `uint32` values. These
  *  rules may also be applied to the `google.protobuf.UInt32Value` Well-Known-Type.
  *
  */
@@ -859,7 +899,7 @@ export interface UInt32Rules {
      *  ```proto
      *  message MyUInt32 {
      *    // value must be in list [1, 2, 3]
-     *    repeated uint32 value = 1 (buf.validate.field).uint32 = { in: [1, 2, 3] };
+     *    uint32 value = 1 [(buf.validate.field).uint32 = { in: [1, 2, 3] }];
      *  }
      *  ```
      *
@@ -873,7 +913,7 @@ export interface UInt32Rules {
      *  ```proto
      *  message MyUInt32 {
      *    // value must not be in list [1, 2, 3]
-     *    repeated uint32 value = 1 (buf.validate.field).uint32 = { not_in: [1, 2, 3] };
+     *    uint32 value = 1 [(buf.validate.field).uint32 = { not_in: [1, 2, 3] }];
      *  }
      *  ```
      *
@@ -881,7 +921,7 @@ export interface UInt32Rules {
     notIn: number[];
     /**
      *  `example` specifies values that the field may have. These values SHOULD
-     *  conform to other constraints. `example` values will not impact validation
+     *  conform to other rules. `example` values will not impact validation
      *  but may be used as helpful guidance on how to populate the given field.
      *
      *  ```proto
@@ -912,7 +952,7 @@ export interface UInt32Rules {
 }
 export declare const UInt32Rules: MessageFns<UInt32Rules, "buf.validate.UInt32Rules">;
 /**
- *  UInt64Rules describes the constraints applied to `uint64` values. These
+ *  UInt64Rules describes the rules applied to `uint64` values. These
  *  rules may also be applied to the `google.protobuf.UInt64Value` Well-Known-Type.
  *
  */
@@ -941,7 +981,7 @@ export interface UInt64Rules {
      *  ```proto
      *  message MyUInt64 {
      *    // value must be in list [1, 2, 3]
-     *    repeated uint64 value = 1 (buf.validate.field).uint64 = { in: [1, 2, 3] };
+     *    uint64 value = 1 [(buf.validate.field).uint64 = { in: [1, 2, 3] }];
      *  }
      *  ```
      *
@@ -955,7 +995,7 @@ export interface UInt64Rules {
      *  ```proto
      *  message MyUInt64 {
      *    // value must not be in list [1, 2, 3]
-     *    repeated uint64 value = 1 (buf.validate.field).uint64 = { not_in: [1, 2, 3] };
+     *    uint64 value = 1 [(buf.validate.field).uint64 = { not_in: [1, 2, 3] }];
      *  }
      *  ```
      *
@@ -963,7 +1003,7 @@ export interface UInt64Rules {
     notIn: Long[];
     /**
      *  `example` specifies values that the field may have. These values SHOULD
-     *  conform to other constraints. `example` values will not impact validation
+     *  conform to other rules. `example` values will not impact validation
      *  but may be used as helpful guidance on how to populate the given field.
      *
      *  ```proto
@@ -994,7 +1034,7 @@ export interface UInt64Rules {
 }
 export declare const UInt64Rules: MessageFns<UInt64Rules, "buf.validate.UInt64Rules">;
 /**
- *  SInt32Rules describes the constraints applied to `sint32` values.
+ *  SInt32Rules describes the rules applied to `sint32` values.
  *
  */
 export interface SInt32Rules {
@@ -1022,7 +1062,7 @@ export interface SInt32Rules {
      *  ```proto
      *  message MySInt32 {
      *    // value must be in list [1, 2, 3]
-     *    repeated sint32 value = 1 (buf.validate.field).sint32 = { in: [1, 2, 3] };
+     *    sint32 value = 1 [(buf.validate.field).sint32 = { in: [1, 2, 3] }];
      *  }
      *  ```
      *
@@ -1036,7 +1076,7 @@ export interface SInt32Rules {
      *  ```proto
      *  message MySInt32 {
      *    // value must not be in list [1, 2, 3]
-     *    repeated sint32 value = 1 (buf.validate.field).sint32 = { not_in: [1, 2, 3] };
+     *    sint32 value = 1 [(buf.validate.field).sint32 = { not_in: [1, 2, 3] }];
      *  }
      *  ```
      *
@@ -1044,7 +1084,7 @@ export interface SInt32Rules {
     notIn: number[];
     /**
      *  `example` specifies values that the field may have. These values SHOULD
-     *  conform to other constraints. `example` values will not impact validation
+     *  conform to other rules. `example` values will not impact validation
      *  but may be used as helpful guidance on how to populate the given field.
      *
      *  ```proto
@@ -1075,7 +1115,7 @@ export interface SInt32Rules {
 }
 export declare const SInt32Rules: MessageFns<SInt32Rules, "buf.validate.SInt32Rules">;
 /**
- *  SInt64Rules describes the constraints applied to `sint64` values.
+ *  SInt64Rules describes the rules applied to `sint64` values.
  *
  */
 export interface SInt64Rules {
@@ -1103,7 +1143,7 @@ export interface SInt64Rules {
      *  ```proto
      *  message MySInt64 {
      *    // value must be in list [1, 2, 3]
-     *    repeated sint64 value = 1 (buf.validate.field).sint64 = { in: [1, 2, 3] };
+     *    sint64 value = 1 [(buf.validate.field).sint64 = { in: [1, 2, 3] }];
      *  }
      *  ```
      *
@@ -1117,7 +1157,7 @@ export interface SInt64Rules {
      *  ```proto
      *  message MySInt64 {
      *    // value must not be in list [1, 2, 3]
-     *    repeated sint64 value = 1 (buf.validate.field).sint64 = { not_in: [1, 2, 3] };
+     *    sint64 value = 1 [(buf.validate.field).sint64 = { not_in: [1, 2, 3] }];
      *  }
      *  ```
      *
@@ -1125,7 +1165,7 @@ export interface SInt64Rules {
     notIn: Long[];
     /**
      *  `example` specifies values that the field may have. These values SHOULD
-     *  conform to other constraints. `example` values will not impact validation
+     *  conform to other rules. `example` values will not impact validation
      *  but may be used as helpful guidance on how to populate the given field.
      *
      *  ```proto
@@ -1156,7 +1196,7 @@ export interface SInt64Rules {
 }
 export declare const SInt64Rules: MessageFns<SInt64Rules, "buf.validate.SInt64Rules">;
 /**
- *  Fixed32Rules describes the constraints applied to `fixed32` values.
+ *  Fixed32Rules describes the rules applied to `fixed32` values.
  *
  */
 export interface Fixed32Rules {
@@ -1184,7 +1224,7 @@ export interface Fixed32Rules {
      *  ```proto
      *  message MyFixed32 {
      *    // value must be in list [1, 2, 3]
-     *    repeated fixed32 value = 1 (buf.validate.field).fixed32 = { in: [1, 2, 3] };
+     *    fixed32 value = 1 [(buf.validate.field).fixed32 = { in: [1, 2, 3] }];
      *  }
      *  ```
      *
@@ -1198,7 +1238,7 @@ export interface Fixed32Rules {
      *  ```proto
      *  message MyFixed32 {
      *    // value must not be in list [1, 2, 3]
-     *    repeated fixed32 value = 1 (buf.validate.field).fixed32 = { not_in: [1, 2, 3] };
+     *    fixed32 value = 1 [(buf.validate.field).fixed32 = { not_in: [1, 2, 3] }];
      *  }
      *  ```
      *
@@ -1206,7 +1246,7 @@ export interface Fixed32Rules {
     notIn: number[];
     /**
      *  `example` specifies values that the field may have. These values SHOULD
-     *  conform to other constraints. `example` values will not impact validation
+     *  conform to other rules. `example` values will not impact validation
      *  but may be used as helpful guidance on how to populate the given field.
      *
      *  ```proto
@@ -1237,7 +1277,7 @@ export interface Fixed32Rules {
 }
 export declare const Fixed32Rules: MessageFns<Fixed32Rules, "buf.validate.Fixed32Rules">;
 /**
- *  Fixed64Rules describes the constraints applied to `fixed64` values.
+ *  Fixed64Rules describes the rules applied to `fixed64` values.
  *
  */
 export interface Fixed64Rules {
@@ -1265,7 +1305,7 @@ export interface Fixed64Rules {
      *  ```proto
      *  message MyFixed64 {
      *    // value must be in list [1, 2, 3]
-     *    repeated fixed64 value = 1 (buf.validate.field).fixed64 = { in: [1, 2, 3] };
+     *    fixed64 value = 1 [(buf.validate.field).fixed64 = { in: [1, 2, 3] }];
      *  }
      *  ```
      *
@@ -1279,7 +1319,7 @@ export interface Fixed64Rules {
      *  ```proto
      *  message MyFixed64 {
      *    // value must not be in list [1, 2, 3]
-     *    repeated fixed64 value = 1 (buf.validate.field).fixed64 = { not_in: [1, 2, 3] };
+     *    fixed64 value = 1 [(buf.validate.field).fixed64 = { not_in: [1, 2, 3] }];
      *  }
      *  ```
      *
@@ -1287,7 +1327,7 @@ export interface Fixed64Rules {
     notIn: Long[];
     /**
      *  `example` specifies values that the field may have. These values SHOULD
-     *  conform to other constraints. `example` values will not impact validation
+     *  conform to other rules. `example` values will not impact validation
      *  but may be used as helpful guidance on how to populate the given field.
      *
      *  ```proto
@@ -1318,7 +1358,7 @@ export interface Fixed64Rules {
 }
 export declare const Fixed64Rules: MessageFns<Fixed64Rules, "buf.validate.Fixed64Rules">;
 /**
- *  SFixed32Rules describes the constraints applied to `fixed32` values.
+ *  SFixed32Rules describes the rules applied to `fixed32` values.
  *
  */
 export interface SFixed32Rules {
@@ -1346,7 +1386,7 @@ export interface SFixed32Rules {
      *  ```proto
      *  message MySFixed32 {
      *    // value must be in list [1, 2, 3]
-     *    repeated sfixed32 value = 1 (buf.validate.field).sfixed32 = { in: [1, 2, 3] };
+     *    sfixed32 value = 1 [(buf.validate.field).sfixed32 = { in: [1, 2, 3] }];
      *  }
      *  ```
      *
@@ -1360,7 +1400,7 @@ export interface SFixed32Rules {
      *  ```proto
      *  message MySFixed32 {
      *    // value must not be in list [1, 2, 3]
-     *    repeated sfixed32 value = 1 (buf.validate.field).sfixed32 = { not_in: [1, 2, 3] };
+     *    sfixed32 value = 1 [(buf.validate.field).sfixed32 = { not_in: [1, 2, 3] }];
      *  }
      *  ```
      *
@@ -1368,7 +1408,7 @@ export interface SFixed32Rules {
     notIn: number[];
     /**
      *  `example` specifies values that the field may have. These values SHOULD
-     *  conform to other constraints. `example` values will not impact validation
+     *  conform to other rules. `example` values will not impact validation
      *  but may be used as helpful guidance on how to populate the given field.
      *
      *  ```proto
@@ -1399,7 +1439,7 @@ export interface SFixed32Rules {
 }
 export declare const SFixed32Rules: MessageFns<SFixed32Rules, "buf.validate.SFixed32Rules">;
 /**
- *  SFixed64Rules describes the constraints applied to `fixed64` values.
+ *  SFixed64Rules describes the rules applied to `fixed64` values.
  *
  */
 export interface SFixed64Rules {
@@ -1427,7 +1467,7 @@ export interface SFixed64Rules {
      *  ```proto
      *  message MySFixed64 {
      *    // value must be in list [1, 2, 3]
-     *    repeated sfixed64 value = 1 (buf.validate.field).sfixed64 = { in: [1, 2, 3] };
+     *    sfixed64 value = 1 [(buf.validate.field).sfixed64 = { in: [1, 2, 3] }];
      *  }
      *  ```
      *
@@ -1441,7 +1481,7 @@ export interface SFixed64Rules {
      *  ```proto
      *  message MySFixed64 {
      *    // value must not be in list [1, 2, 3]
-     *    repeated sfixed64 value = 1 (buf.validate.field).sfixed64 = { not_in: [1, 2, 3] };
+     *    sfixed64 value = 1 [(buf.validate.field).sfixed64 = { not_in: [1, 2, 3] }];
      *  }
      *  ```
      *
@@ -1449,7 +1489,7 @@ export interface SFixed64Rules {
     notIn: Long[];
     /**
      *  `example` specifies values that the field may have. These values SHOULD
-     *  conform to other constraints. `example` values will not impact validation
+     *  conform to other rules. `example` values will not impact validation
      *  but may be used as helpful guidance on how to populate the given field.
      *
      *  ```proto
@@ -1480,7 +1520,7 @@ export interface SFixed64Rules {
 }
 export declare const SFixed64Rules: MessageFns<SFixed64Rules, "buf.validate.SFixed64Rules">;
 /**
- *  BoolRules describes the constraints applied to `bool` values. These rules
+ *  BoolRules describes the rules applied to `bool` values. These rules
  *  may also be applied to the `google.protobuf.BoolValue` Well-Known-Type.
  *
  */
@@ -1503,7 +1543,7 @@ export interface BoolRules {
     const?: boolean | undefined;
     /**
      *  `example` specifies values that the field may have. These values SHOULD
-     *  conform to other constraints. `example` values will not impact validation
+     *  conform to other rules. `example` values will not impact validation
      *  but may be used as helpful guidance on how to populate the given field.
      *
      *  ```proto
@@ -1520,7 +1560,7 @@ export interface BoolRules {
 }
 export declare const BoolRules: MessageFns<BoolRules, "buf.validate.BoolRules">;
 /**
- *  StringRules describes the constraints applied to `string` values These
+ *  StringRules describes the rules applied to `string` values These
  *  rules may also be applied to the `google.protobuf.StringValue` Well-Known-Type.
  *
  */
@@ -1709,7 +1749,7 @@ export interface StringRules {
      *  ```proto
      *  message MyString {
      *    // value must be in list ["apple", "banana"]
-     *    repeated string value = 1 [(buf.validate.field).string.in = "apple", (buf.validate.field).string.in = "banana"];
+     *    string value = 1 [(buf.validate.field).string.in = "apple", (buf.validate.field).string.in = "banana"];
      *  }
      *  ```
      *
@@ -1722,7 +1762,7 @@ export interface StringRules {
      *  ```proto
      *  message MyString {
      *    // value must not be in list ["orange", "grape"]
-     *    repeated string value = 1 [(buf.validate.field).string.not_in = "orange", (buf.validate.field).string.not_in = "grape"];
+     *    string value = 1 [(buf.validate.field).string.not_in = "orange", (buf.validate.field).string.not_in = "grape"];
      *  }
      *  ```
      *
@@ -1731,7 +1771,7 @@ export interface StringRules {
     /**
      *  This applies to regexes `HTTP_HEADER_NAME` and `HTTP_HEADER_VALUE` to
      *  enable strict header validation. By default, this is true, and HTTP header
-     *  validations are [RFC-compliant](https://tools.ietf.org/html/rfc7230#section-3). Setting to false will enable looser
+     *  validations are [RFC-compliant](https://datatracker.ietf.org/doc/html/rfc7230#section-3). Setting to false will enable looser
      *  validations that only disallow `\r\n\0` characters, which can be used to
      *  bypass header matching rules.
      *
@@ -1746,7 +1786,7 @@ export interface StringRules {
     strict?: boolean | undefined;
     /**
      *  `example` specifies values that the field may have. These values SHOULD
-     *  conform to other constraints. `example` values will not impact validation
+     *  conform to other rules. `example` values will not impact validation
      *  but may be used as helpful guidance on how to populate the given field.
      *
      *  ```proto
@@ -1761,8 +1801,8 @@ export interface StringRules {
      */
     example: string[];
     /**
-     *  `WellKnown` rules provide advanced constraints against common string
-     *  patterns
+     *  `WellKnown` rules provide advanced rules against common string
+     *  patterns.
      *
      */
     wellKnown?: {
@@ -1816,6 +1856,9 @@ export interface StringRules {
     } | {
         $case: "hostAndPort";
         hostAndPort: boolean;
+    } | {
+        $case: "ulid";
+        ulid: boolean;
     } | {
         $case: "wellKnownRegex";
         wellKnownRegex: KnownRegex;
@@ -1823,7 +1866,7 @@ export interface StringRules {
 }
 export declare const StringRules: MessageFns<StringRules, "buf.validate.StringRules">;
 /**
- *  BytesRules describe the constraints applied to `bytes` values. These rules
+ *  BytesRules describe the rules applied to `bytes` values. These rules
  *  may also be applied to the `google.protobuf.BytesValue` Well-Known-Type.
  *
  */
@@ -1934,7 +1977,7 @@ export interface BytesRules {
      *  the string.
      *  If the field value doesn't meet the requirement, an error message is generated.
      *
-     *  ```protobuf
+     *  ```proto
      *  message MyBytes {
      *    // value does not contain \x02\x03
      *    optional bytes value = 1 [(buf.validate.field).bytes.contains = "\x02\x03"];
@@ -1948,7 +1991,7 @@ export interface BytesRules {
      *  values. If the field value doesn't match any of the specified values, an
      *  error message is generated.
      *
-     *  ```protobuf
+     *  ```proto
      *  message MyBytes {
      *    // value must in ["\x01\x02", "\x02\x03", "\x03\x04"]
      *    optional bytes value = 1 [(buf.validate.field).bytes.in = {"\x01\x02", "\x02\x03", "\x03\x04"}];
@@ -1974,7 +2017,7 @@ export interface BytesRules {
     notIn: Uint8Array[];
     /**
      *  `example` specifies values that the field may have. These values SHOULD
-     *  conform to other constraints. `example` values will not impact validation
+     *  conform to other rules. `example` values will not impact validation
      *  but may be used as helpful guidance on how to populate the given field.
      *
      *  ```proto
@@ -1989,7 +2032,7 @@ export interface BytesRules {
      */
     example: Uint8Array[];
     /**
-     *  WellKnown rules provide advanced constraints against common byte
+     *  WellKnown rules provide advanced rules against common byte
      *  patterns
      *
      */
@@ -2002,11 +2045,14 @@ export interface BytesRules {
     } | {
         $case: "ipv6";
         ipv6: boolean;
+    } | {
+        $case: "uuid";
+        uuid: boolean;
     } | undefined;
 }
 export declare const BytesRules: MessageFns<BytesRules, "buf.validate.BytesRules">;
 /**
- *  EnumRules describe the constraints applied to `enum` values.
+ *  EnumRules describe the rules applied to `enum` values.
  *
  */
 export interface EnumRules {
@@ -2093,7 +2139,7 @@ export interface EnumRules {
     notIn: number[];
     /**
      *  `example` specifies values that the field may have. These values SHOULD
-     *  conform to other constraints. `example` values will not impact validation
+     *  conform to other rules. `example` values will not impact validation
      *  but may be used as helpful guidance on how to populate the given field.
      *
      *  ```proto
@@ -2114,7 +2160,7 @@ export interface EnumRules {
 }
 export declare const EnumRules: MessageFns<EnumRules, "buf.validate.EnumRules">;
 /**
- *  RepeatedRules describe the constraints applied to `repeated` values.
+ *  RepeatedRules describe the rules applied to `repeated` values.
  *
  */
 export interface RepeatedRules {
@@ -2153,7 +2199,7 @@ export interface RepeatedRules {
     maxItems?: Long | undefined;
     /**
      *  `unique` indicates that all elements in this field must
-     *  be unique. This constraint is strictly applicable to scalar and enum
+     *  be unique. This rule is strictly applicable to scalar and enum
      *  types, with message types not being supported.
      *
      *  ```proto
@@ -2166,13 +2212,13 @@ export interface RepeatedRules {
      */
     unique?: boolean | undefined;
     /**
-     *  `items` details the constraints to be applied to each item
+     *  `items` details the rules to be applied to each item
      *  in the field. Even for repeated message fields, validation is executed
-     *  against each item unless skip is explicitly specified.
+     *  against each item unless `ignore` is specified.
      *
      *  ```proto
      *  message MyRepeated {
-     *    // The items in the field `value` must follow the specified constraints.
+     *    // The items in the field `value` must follow the specified rules.
      *    repeated string value = 1 [(buf.validate.field).repeated.items = {
      *      string: {
      *        min_len: 3
@@ -2182,12 +2228,15 @@ export interface RepeatedRules {
      *  }
      *  ```
      *
+     *  Note that the `required` rule does not apply. Repeated items
+     *  cannot be unset.
+     *
      */
-    items?: FieldConstraints | undefined;
+    items?: FieldRules | undefined;
 }
 export declare const RepeatedRules: MessageFns<RepeatedRules, "buf.validate.RepeatedRules">;
 /**
- *  MapRules describe the constraints applied to `map` values.
+ *  MapRules describe the rules applied to `map` values.
  *
  */
 export interface MapRules {
@@ -2195,7 +2244,7 @@ export interface MapRules {
     [unknownFieldsSymbol]?: Uint8Array | undefined;
     [customJson]?: () => unknown;
     /**
-     * Specifies the minimum number of key-value pairs allowed. If the field has
+     *  Specifies the minimum number of key-value pairs allowed. If the field has
      *  fewer key-value pairs than specified, an error message is generated.
      *
      *  ```proto
@@ -2208,7 +2257,7 @@ export interface MapRules {
      */
     minPairs?: Long | undefined;
     /**
-     * Specifies the maximum number of key-value pairs allowed. If the field has
+     *  Specifies the maximum number of key-value pairs allowed. If the field has
      *  more key-value pairs than specified, an error message is generated.
      *
      *  ```proto
@@ -2221,11 +2270,11 @@ export interface MapRules {
      */
     maxPairs?: Long | undefined;
     /**
-     * Specifies the constraints to be applied to each key in the field.
+     *  Specifies the rules to be applied to each key in the field.
      *
      *  ```proto
      *  message MyMap {
-     *    // The keys in the field `value` must follow the specified constraints.
+     *    // The keys in the field `value` must follow the specified rules.
      *    map<string, string> value = 1 [(buf.validate.field).map.keys = {
      *      string: {
      *        min_len: 3
@@ -2235,16 +2284,18 @@ export interface MapRules {
      *  }
      *  ```
      *
+     *  Note that the `required` rule does not apply. Map keys cannot be unset.
+     *
      */
-    keys?: FieldConstraints | undefined;
+    keys?: FieldRules | undefined;
     /**
-     * Specifies the constraints to be applied to the value of each key in the
+     *  Specifies the rules to be applied to the value of each key in the
      *  field. Message values will still have their validations evaluated unless
-     * skip is specified here.
+     *  `ignore` is specified.
      *
      *  ```proto
      *  message MyMap {
-     *    // The values in the field `value` must follow the specified constraints.
+     *    // The values in the field `value` must follow the specified rules.
      *    map<string, string> value = 1 [(buf.validate.field).map.values = {
      *      string: {
      *        min_len: 5
@@ -2253,13 +2304,14 @@ export interface MapRules {
      *    }];
      *  }
      *  ```
+     *  Note that the `required` rule does not apply. Map values cannot be unset.
      *
      */
-    values?: FieldConstraints | undefined;
+    values?: FieldRules | undefined;
 }
 export declare const MapRules: MessageFns<MapRules, "buf.validate.MapRules">;
 /**
- *  AnyRules describe constraints applied exclusively to the `google.protobuf.Any` well-known type.
+ *  AnyRules describe rules applied exclusively to the `google.protobuf.Any` well-known type.
  *
  */
 export interface AnyRules {
@@ -2274,7 +2326,9 @@ export interface AnyRules {
      *  ```proto
      *  message MyAny {
      *    //  The `value` field must have a `type_url` equal to one of the specified values.
-     *    google.protobuf.Any value = 1 [(buf.validate.field).any.in = ["type.googleapis.com/MyType1", "type.googleapis.com/MyType2"]];
+     *    google.protobuf.Any value = 1 [(buf.validate.field).any = {
+     *        in: ["type.googleapis.com/MyType1", "type.googleapis.com/MyType2"]
+     *    }];
      *  }
      *  ```
      *
@@ -2285,8 +2339,10 @@ export interface AnyRules {
      *
      *  ```proto
      *  message MyAny {
-     *    // The field `value` must not have a `type_url` equal to any of the specified values.
-     *    google.protobuf.Any value = 1 [(buf.validate.field).any.not_in = ["type.googleapis.com/ForbiddenType1", "type.googleapis.com/ForbiddenType2"]];
+     *    //  The `value` field must not have a `type_url` equal to any of the specified values.
+     *    google.protobuf.Any value = 1 [(buf.validate.field).any = {
+     *        not_in: ["type.googleapis.com/ForbiddenType1", "type.googleapis.com/ForbiddenType2"]
+     *    }];
      *  }
      *  ```
      *
@@ -2295,7 +2351,7 @@ export interface AnyRules {
 }
 export declare const AnyRules: MessageFns<AnyRules, "buf.validate.AnyRules">;
 /**
- *  DurationRules describe the constraints applied exclusively to the `google.protobuf.Duration` well-known type.
+ *  DurationRules describe the rules applied exclusively to the `google.protobuf.Duration` well-known type.
  *
  */
 export interface DurationRules {
@@ -2347,7 +2403,7 @@ export interface DurationRules {
     notIn: Duration[];
     /**
      *  `example` specifies values that the field may have. These values SHOULD
-     *  conform to other constraints. `example` values will not impact validation
+     *  conform to other rules. `example` values will not impact validation
      *  but may be used as helpful guidance on how to populate the given field.
      *
      *  ```proto
@@ -2378,7 +2434,85 @@ export interface DurationRules {
 }
 export declare const DurationRules: MessageFns<DurationRules, "buf.validate.DurationRules">;
 /**
- *  TimestampRules describe the constraints applied exclusively to the `google.protobuf.Timestamp` well-known type.
+ *  FieldMaskRules describe rules applied exclusively to the `google.protobuf.FieldMask` well-known type.
+ *
+ */
+export interface FieldMaskRules {
+    $type: "buf.validate.FieldMaskRules";
+    [unknownFieldsSymbol]?: Uint8Array | undefined;
+    [customJson]?: () => unknown;
+    /**
+     *  `const` dictates that the field must match the specified value of the `google.protobuf.FieldMask` type exactly.
+     *  If the field's value deviates from the specified value, an error message
+     *  will be generated.
+     *
+     *  ```proto
+     *  message MyFieldMask {
+     *    // value must equal ["a"]
+     *    google.protobuf.FieldMask value = 1 [(buf.validate.field).field_mask.const = {
+     *        paths: ["a"]
+     *    }];
+     *  }
+     *  ```
+     *
+     */
+    const?: string[] | undefined;
+    /**
+     *  `in` requires the field value to only contain paths matching specified
+     *  values or their subpaths.
+     *  If any of the field value's paths doesn't match the rule,
+     *  an error message is generated.
+     *  See: https://protobuf.dev/reference/protobuf/google.protobuf/#field-mask
+     *
+     *  ```proto
+     *  message MyFieldMask {
+     *    //  The `value` FieldMask must only contain paths listed in `in`.
+     *    google.protobuf.FieldMask value = 1 [(buf.validate.field).field_mask = {
+     *        in: ["a", "b", "c.a"]
+     *    }];
+     *  }
+     *  ```
+     *
+     */
+    in: string[];
+    /**
+     *  `not_in` requires the field value to not contain paths matching specified
+     *  values or their subpaths.
+     *  If any of the field value's paths matches the rule,
+     *  an error message is generated.
+     *  See: https://protobuf.dev/reference/protobuf/google.protobuf/#field-mask
+     *
+     *  ```proto
+     *  message MyFieldMask {
+     *    //  The `value` FieldMask shall not contain paths listed in `not_in`.
+     *    google.protobuf.FieldMask value = 1 [(buf.validate.field).field_mask = {
+     *        not_in: ["forbidden", "immutable", "c.a"]
+     *    }];
+     *  }
+     *  ```
+     *
+     */
+    notIn: string[];
+    /**
+     *  `example` specifies values that the field may have. These values SHOULD
+     *  conform to other rules. `example` values will not impact validation
+     *  but may be used as helpful guidance on how to populate the given field.
+     *
+     *  ```proto
+     *  message MyFieldMask {
+     *    google.protobuf.FieldMask value = 1 [
+     *      (buf.validate.field).field_mask.example = { paths: ["a", "b"] },
+     *      (buf.validate.field).field_mask.example = { paths: ["c.a", "d"] },
+     *    ];
+     *  }
+     *  ```
+     *
+     */
+    example: string[][];
+}
+export declare const FieldMaskRules: MessageFns<FieldMaskRules, "buf.validate.FieldMaskRules">;
+/**
+ *  TimestampRules describe the rules applied exclusively to the `google.protobuf.Timestamp` well-known type.
  *
  */
 export interface TimestampRules {
@@ -2411,7 +2545,7 @@ export interface TimestampRules {
     within?: Duration | undefined;
     /**
      *  `example` specifies values that the field may have. These values SHOULD
-     *  conform to other constraints. `example` values will not impact validation
+     *  conform to other rules. `example` values will not impact validation
      *  but may be used as helpful guidance on how to populate the given field.
      *
      *  ```proto
@@ -2449,7 +2583,7 @@ export interface TimestampRules {
 export declare const TimestampRules: MessageFns<TimestampRules, "buf.validate.TimestampRules">;
 /**
  *  `Violations` is a collection of `Violation` messages. This message type is returned by
- *  protovalidate when a proto message fails to meet the requirements set by the `Constraint` validation rules.
+ *  Protovalidate when a proto message fails to meet the requirements set by the `Rule` validation rules.
  *  Each individual violation is represented by a `Violation` message.
  *
  */
@@ -2466,15 +2600,46 @@ export interface Violations {
 export declare const Violations: MessageFns<Violations, "buf.validate.Violations">;
 /**
  *  `Violation` represents a single instance where a validation rule, expressed
- *  as a `Constraint`, was not met. It provides information about the field that
- *  caused the violation, the specific constraint that wasn't fulfilled, and a
+ *  as a `Rule`, was not met. It provides information about the field that
+ *  caused the violation, the specific rule that wasn't fulfilled, and a
  *  human-readable error message.
  *
+ *  For example, consider the following message:
+ *
+ *  ```proto
+ *  message User {
+ *      int32 age = 1 [(buf.validate.field).cel = {
+ *          id: "user.age",
+ *          expression: "this < 18 ? 'User must be at least 18 years old' : ''",
+ *      }];
+ *  }
+ *  ```
+ *
+ *  It could produce the following violation:
+ *
  *  ```json
  *  {
- *    "fieldPath": "bar",
- *    "constraintId": "foo.bar",
- *    "message": "bar must be greater than 0"
+ *    "ruleId": "user.age",
+ *    "message": "User must be at least 18 years old",
+ *    "field": {
+ *      "elements": [
+ *        {
+ *          "fieldNumber": 1,
+ *          "fieldName": "age",
+ *          "fieldType": "TYPE_INT32"
+ *        }
+ *      ]
+ *    },
+ *    "rule": {
+ *      "elements": [
+ *        {
+ *          "fieldNumber": 23,
+ *          "fieldName": "cel",
+ *          "fieldType": "TYPE_MESSAGE",
+ *          "index": "0"
+ *        }
+ *      ]
+ *    }
  *  }
  *  ```
  *
@@ -2507,9 +2672,9 @@ export interface Violation {
      */
     field?: FieldPath | undefined;
     /**
-     *  `rule` is a machine-readable path that points to the specific constraint rule that failed validation.
-     *  This will be a nested field starting from the FieldConstraints of the field that failed validation.
-     *  For custom constraints, this will provide the path of the constraint, e.g. `cel[0]`.
+     *  `rule` is a machine-readable path that points to the specific rule that failed validation.
+     *  This will be a nested field starting from the FieldRules of the field that failed validation.
+     *  For custom rules, this will provide the path of the rule, e.g. `cel[0]`.
      *
      *  For example, consider the following message:
      *
@@ -2517,7 +2682,7 @@ export interface Violation {
      *  message Message {
      *    bool a = 1 [(buf.validate.field).required = true];
      *    bool b = 2 [(buf.validate.field).cel = {
-     *      id: "custom_constraint",
+     *      id: "custom_rule",
      *      expression: "!this ? 'b must be true': ''"
      *    }]
      *  }
@@ -2539,23 +2704,14 @@ export interface Violation {
      */
     rule?: FieldPath | undefined;
     /**
-     *  `field_path` is a human-readable identifier that points to the specific field that failed the validation.
-     *  This could be a nested field, in which case the path will include all the parent fields leading to the actual field that caused the violation.
-     *
-     *  Deprecated: use the `field` instead.
-     *
-     * @deprecated Deprecated.
-     */
-    fieldPath?: string | undefined;
-    /**
-     *  `constraint_id` is the unique identifier of the `Constraint` that was not fulfilled.
-     *  This is the same `id` that was specified in the `Constraint` message, allowing easy tracing of which rule was violated.
+     *  `rule_id` is the unique identifier of the `Rule` that was not fulfilled.
+     *  This is the same `id` that was specified in the `Rule` message, allowing easy tracing of which rule was violated.
      *
      */
-    constraintId?: string | undefined;
+    ruleId?: string | undefined;
     /**
      *  `message` is a human-readable error message that describes the nature of the violation.
-     *  This can be the default error message from the violated `Constraint`, or it can be a custom message that gives more context about the violation.
+     *  This can be the default error message from the violated `Rule`, or it can be a custom message that gives more context about the violation.
      *
      */
     message?: string | undefined;
@@ -2659,22 +2815,22 @@ export declare const FieldPathElement: MessageFns<FieldPathElement, "buf.validat
 import "../../google/protobuf/index";
 declare module '../../google/protobuf/index' {
     interface MessageOptions {
-        message?: MessageConstraints;
+        message?: MessageRules;
     }
 }
 declare module '../../google/protobuf/index' {
     interface OneofOptions {
-        oneof?: OneofConstraints;
+        oneof?: OneofRules;
     }
 }
 declare module '../../google/protobuf/index' {
     interface FieldOptions {
-        field?: FieldConstraints;
+        field?: FieldRules;
     }
 }
 declare module '../../google/protobuf/index' {
     interface FieldOptions {
-        predefined?: PredefinedConstraints;
+        predefined?: PredefinedRules;
     }
 }
 export {};