google-apis-firestore_v1 0.98.0 → 0.100.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: e38fb2c8c7e43e9d57eec4549930966b9d579ccd7b9643c835102310b9156d3b
-  data.tar.gz: 774baa20de59cd65f2009ea06f62521b21fe5db143edac628e76658baec352f5
+  metadata.gz: b1fead599ce1cf026ef2d00b7112b4c3da820a4d707df0f769df07fe53fcfc24
+  data.tar.gz: 1bfcaa09f08ed411bcec3745a1e53130c15a78f75d4fa3cf6e95d0b365853a7c
 SHA512:
-  metadata.gz: 8b5c4ec803932ffe9ddbb6a379c002ba31eef47182d2c1695fd6644070fd398b86f767292858ddded18db9311f58e4ed7bcd127448c3e8be102ed9648c42284f
-  data.tar.gz: db9f4b2b99ce8f5c293d37dcdea18ef736e0c8f7bafd662f519d911c78a893a1ddd566db8d3284af4c35b366b36623764a3b1d9d800c5687445a2c8261426600
+  metadata.gz: 7651ddcde70802c50cf69f1527489cf2dcf5f180839e0f12e0b16854d37f0c41aaa63bbf8fff17805374430fc144fe7342a6fe6f3203b8bfbe5bfd65bea807c7
+  data.tar.gz: d9de0b293b319e46d86487dd1635bfda98a66d172328348048afc10087fef46ad84d4362db1e2a43b4421a1d32191da7b59468eebffffc6f158e9435d832f431

data/CHANGELOG.md

@@ -1,5 +1,13 @@
 # Release history for google-apis-firestore_v1
 
+### v0.100.0 (2026-09-20)
+
+* Regenerated from discovery document revision 20260826
+
+### v0.99.0 (2026-08-30)
+
+* Regenerated from discovery document revision 20260818
+
 ### v0.98.0 (2026-08-23)
 
 * Regenerated from discovery document revision 20260810

data/lib/google/apis/firestore_v1/classes.rb

@@ -180,7 +180,7 @@ module Google
         # @return [String]
         attr_accessor :read_time
       
-        # Options for a server request.
+        # Options for a request.
         # Corresponds to the JSON property `requestOptions`
         # @return [Google::Apis::FirestoreV1::RequestOptions]
         attr_accessor :request_options
@@ -258,7 +258,7 @@ module Google
         # @return [Hash<String,String>]
         attr_accessor :labels
       
-        # Options for a server request.
+        # Options for a request.
         # Corresponds to the JSON property `requestOptions`
         # @return [Google::Apis::FirestoreV1::RequestOptions]
         attr_accessor :request_options
@@ -318,7 +318,7 @@ module Google
         # @return [Google::Apis::FirestoreV1::TransactionOptions]
         attr_accessor :options
       
-        # Options for a server request.
+        # Options for a request.
         # Corresponds to the JSON property `requestOptions`
         # @return [Google::Apis::FirestoreV1::RequestOptions]
         attr_accessor :request_options
@@ -468,7 +468,7 @@ module Google
       class CommitRequest
         include Google::Apis::Core::Hashable
       
-        # Options for a server request.
+        # Options for a request.
         # Corresponds to the JSON property `requestOptions`
         # @return [Google::Apis::FirestoreV1::RequestOptions]
         attr_accessor :request_options
@@ -875,7 +875,7 @@ module Google
         # @return [String]
         attr_accessor :read_time
       
-        # Options for a server request.
+        # Options for a request.
         # Corresponds to the JSON property `requestOptions`
         # @return [Google::Apis::FirestoreV1::RequestOptions]
         attr_accessor :request_options
@@ -3249,7 +3249,8 @@ module Google
         include Google::Apis::Core::Hashable
       
         # Optional. Disables geoJSON indexing for the field. By default, geoJSON points
-        # are indexed.
+        # are indexed. Firestore GeoPoints are indexed regardless of the value of this
+        # field.
         # Corresponds to the JSON property `geoJsonIndexingDisabled`
         # @return [Boolean]
         attr_accessor :geo_json_indexing_disabled
@@ -3767,7 +3768,7 @@ module Google
         # @return [String]
         attr_accessor :read_time
       
-        # Options for a server request.
+        # Options for a request.
         # Corresponds to the JSON property `requestOptions`
         # @return [Google::Apis::FirestoreV1::RequestOptions]
         attr_accessor :request_options
@@ -3880,7 +3881,7 @@ module Google
         # @return [Fixnum]
         attr_accessor :remove_target
       
-        # Options for a server request.
+        # Options for a request.
         # Corresponds to the JSON property `requestOptions`
         # @return [Google::Apis::FirestoreV1::RequestOptions]
         attr_accessor :request_options
@@ -4088,7 +4089,7 @@ module Google
         # @return [String]
         attr_accessor :read_time
       
-        # Options for a server request.
+        # Options for a request.
         # Corresponds to the JSON property `requestOptions`
         # @return [Google::Apis::FirestoreV1::RequestOptions]
         attr_accessor :request_options
@@ -4321,11 +4322,31 @@ module Google
         end
       end
       
-      # Options for a server request.
+      # Options for a request.
       class RequestOptions
         include Google::Apis::Core::Hashable
       
-        # Optional. The request tags for the request.
+        # Optional. The request tags for the request. Request tags are user-provided
+        # strings used for usage monitoring, cost management, and observability. Callers
+        # can associate custom application context (such as component, microservice,
+        # feature name, or operation type) with database requests. These tags are
+        # collected and aggregated in usage and monitoring reports, allowing billable
+        # operations and usage metrics to be sliced and analyzed by tag. These tags *
+        # only* show up in monitoring and are visible in administrative operations (such
+        # as usage reports). They do not affect data storage, query semantics, or
+        # request execution. Cardinality and Best Practices: - Request tags are most
+        # effective when using a bounded set of distinct values (e.g., fewer than 100
+        # distinct tags across an entire database). Using a large number of distinct
+        # tags may result in tags being omitted from top usage dashboards. - Use
+        # structured identifiers (for example: `app=cart`, `env=prod`, `service=checkout`
+        # ) and avoid high-cardinality values such as UUIDs, request IDs, timestamps,
+        # user IDs, or document keys. - Do not include sensitive data or personally
+        # identifiable information (PII) in request tags, as they show up in
+        # administrative monitoring. The tags are processed as follows: - Leading and
+        # trailing whitespace is trimmed. - Empty tags (after trimming) are filtered out.
+        # - Truncated to a maximum of 510 characters. - Deduplicated within the same
+        # request. - Limited to a maximum of 50 tags per request (excess tags are
+        # silently discarded).
         # Corresponds to the JSON property `requestTags`
         # @return [Array<String>]
         attr_accessor :request_tags
@@ -4344,7 +4365,7 @@ module Google
       class RollbackRequest
         include Google::Apis::Core::Hashable
       
-        # Options for a server request.
+        # Options for a request.
         # Corresponds to the JSON property `requestOptions`
         # @return [Google::Apis::FirestoreV1::RequestOptions]
         attr_accessor :request_options
@@ -4387,7 +4408,7 @@ module Google
         # @return [String]
         attr_accessor :read_time
       
-        # Options for a server request.
+        # Options for a request.
         # Corresponds to the JSON property `requestOptions`
         # @return [Google::Apis::FirestoreV1::RequestOptions]
         attr_accessor :request_options
@@ -4485,7 +4506,7 @@ module Google
         # @return [String]
         attr_accessor :read_time
       
-        # Options for a server request.
+        # Options for a request.
         # Corresponds to the JSON property `requestOptions`
         # @return [Google::Apis::FirestoreV1::RequestOptions]
         attr_accessor :request_options
@@ -5209,7 +5230,7 @@ module Google
         # @return [Hash<String,String>]
         attr_accessor :labels
       
-        # Options for a server request.
+        # Options for a request.
         # Corresponds to the JSON property `requestOptions`
         # @return [Google::Apis::FirestoreV1::RequestOptions]
         attr_accessor :request_options

data/lib/google/apis/firestore_v1/gem_version.rb

@@ -16,13 +16,13 @@ module Google
   module Apis
     module FirestoreV1
       # Version of the google-apis-firestore_v1 gem
-      GEM_VERSION = "0.98.0"
+      GEM_VERSION = "0.100.0"
 
       # Version of the code generator used to generate this client
       GENERATOR_VERSION = "0.19.0"
 
       # Revision of the discovery document this client was generated from
-      REVISION = "20260810"
+      REVISION = "20260826"
     end
   end
 end

data/lib/google/apis/firestore_v1/service.rb

@@ -1168,7 +1168,27 @@ module Google
         #   The list of field paths in the mask. See Document.fields for a field path
         #   syntax reference.
         # @param [Array<String>, String] request_options_request_tags
-        #   Optional. The request tags for the request.
+        #   Optional. The request tags for the request. Request tags are user-provided
+        #   strings used for usage monitoring, cost management, and observability. Callers
+        #   can associate custom application context (such as component, microservice,
+        #   feature name, or operation type) with database requests. These tags are
+        #   collected and aggregated in usage and monitoring reports, allowing billable
+        #   operations and usage metrics to be sliced and analyzed by tag. These tags *
+        #   only* show up in monitoring and are visible in administrative operations (such
+        #   as usage reports). They do not affect data storage, query semantics, or
+        #   request execution. Cardinality and Best Practices: - Request tags are most
+        #   effective when using a bounded set of distinct values (e.g., fewer than 100
+        #   distinct tags across an entire database). Using a large number of distinct
+        #   tags may result in tags being omitted from top usage dashboards. - Use
+        #   structured identifiers (for example: `app=cart`, `env=prod`, `service=checkout`
+        #   ) and avoid high-cardinality values such as UUIDs, request IDs, timestamps,
+        #   user IDs, or document keys. - Do not include sensitive data or personally
+        #   identifiable information (PII) in request tags, as they show up in
+        #   administrative monitoring. The tags are processed as follows: - Leading and
+        #   trailing whitespace is trimmed. - Empty tags (after trimming) are filtered out.
+        #   - Truncated to a maximum of 510 characters. - Deduplicated within the same
+        #   request. - Limited to a maximum of 50 tags per request (excess tags are
+        #   silently discarded).
         # @param [String] fields
         #   Selector specifying which fields to include in a partial response.
         # @param [String] quota_user
@@ -1213,7 +1233,27 @@ module Google
         #   When set, the target document must exist and have been last updated at that
         #   time. Timestamp must be microsecond aligned.
         # @param [Array<String>, String] request_options_request_tags
-        #   Optional. The request tags for the request.
+        #   Optional. The request tags for the request. Request tags are user-provided
+        #   strings used for usage monitoring, cost management, and observability. Callers
+        #   can associate custom application context (such as component, microservice,
+        #   feature name, or operation type) with database requests. These tags are
+        #   collected and aggregated in usage and monitoring reports, allowing billable
+        #   operations and usage metrics to be sliced and analyzed by tag. These tags *
+        #   only* show up in monitoring and are visible in administrative operations (such
+        #   as usage reports). They do not affect data storage, query semantics, or
+        #   request execution. Cardinality and Best Practices: - Request tags are most
+        #   effective when using a bounded set of distinct values (e.g., fewer than 100
+        #   distinct tags across an entire database). Using a large number of distinct
+        #   tags may result in tags being omitted from top usage dashboards. - Use
+        #   structured identifiers (for example: `app=cart`, `env=prod`, `service=checkout`
+        #   ) and avoid high-cardinality values such as UUIDs, request IDs, timestamps,
+        #   user IDs, or document keys. - Do not include sensitive data or personally
+        #   identifiable information (PII) in request tags, as they show up in
+        #   administrative monitoring. The tags are processed as follows: - Leading and
+        #   trailing whitespace is trimmed. - Empty tags (after trimming) are filtered out.
+        #   - Truncated to a maximum of 510 characters. - Deduplicated within the same
+        #   request. - Limited to a maximum of 50 tags per request (excess tags are
+        #   silently discarded).
         # @param [String] fields
         #   Selector specifying which fields to include in a partial response.
         # @param [String] quota_user
@@ -1291,7 +1331,27 @@ module Google
         #   Recovery is enabled, can additionally be a whole minute timestamp within the
         #   past 7 days.
         # @param [Array<String>, String] request_options_request_tags
-        #   Optional. The request tags for the request.
+        #   Optional. The request tags for the request. Request tags are user-provided
+        #   strings used for usage monitoring, cost management, and observability. Callers
+        #   can associate custom application context (such as component, microservice,
+        #   feature name, or operation type) with database requests. These tags are
+        #   collected and aggregated in usage and monitoring reports, allowing billable
+        #   operations and usage metrics to be sliced and analyzed by tag. These tags *
+        #   only* show up in monitoring and are visible in administrative operations (such
+        #   as usage reports). They do not affect data storage, query semantics, or
+        #   request execution. Cardinality and Best Practices: - Request tags are most
+        #   effective when using a bounded set of distinct values (e.g., fewer than 100
+        #   distinct tags across an entire database). Using a large number of distinct
+        #   tags may result in tags being omitted from top usage dashboards. - Use
+        #   structured identifiers (for example: `app=cart`, `env=prod`, `service=checkout`
+        #   ) and avoid high-cardinality values such as UUIDs, request IDs, timestamps,
+        #   user IDs, or document keys. - Do not include sensitive data or personally
+        #   identifiable information (PII) in request tags, as they show up in
+        #   administrative monitoring. The tags are processed as follows: - Leading and
+        #   trailing whitespace is trimmed. - Empty tags (after trimming) are filtered out.
+        #   - Truncated to a maximum of 510 characters. - Deduplicated within the same
+        #   request. - Limited to a maximum of 50 tags per request (excess tags are
+        #   silently discarded).
         # @param [String] transaction
         #   Reads the document in a transaction.
         # @param [String] fields
@@ -1364,7 +1424,27 @@ module Google
         #   nested immediately under the parent. Requests with `recursive` may not specify
         #   `show_missing`.
         # @param [Array<String>, String] request_options_request_tags
-        #   Optional. The request tags for the request.
+        #   Optional. The request tags for the request. Request tags are user-provided
+        #   strings used for usage monitoring, cost management, and observability. Callers
+        #   can associate custom application context (such as component, microservice,
+        #   feature name, or operation type) with database requests. These tags are
+        #   collected and aggregated in usage and monitoring reports, allowing billable
+        #   operations and usage metrics to be sliced and analyzed by tag. These tags *
+        #   only* show up in monitoring and are visible in administrative operations (such
+        #   as usage reports). They do not affect data storage, query semantics, or
+        #   request execution. Cardinality and Best Practices: - Request tags are most
+        #   effective when using a bounded set of distinct values (e.g., fewer than 100
+        #   distinct tags across an entire database). Using a large number of distinct
+        #   tags may result in tags being omitted from top usage dashboards. - Use
+        #   structured identifiers (for example: `app=cart`, `env=prod`, `service=checkout`
+        #   ) and avoid high-cardinality values such as UUIDs, request IDs, timestamps,
+        #   user IDs, or document keys. - Do not include sensitive data or personally
+        #   identifiable information (PII) in request tags, as they show up in
+        #   administrative monitoring. The tags are processed as follows: - Leading and
+        #   trailing whitespace is trimmed. - Empty tags (after trimming) are filtered out.
+        #   - Truncated to a maximum of 510 characters. - Deduplicated within the same
+        #   request. - Limited to a maximum of 50 tags per request (excess tags are
+        #   silently discarded).
         # @param [Boolean] show_missing
         #   If the list should show missing documents. A document is missing if it does
         #   not exist, but there are sub-documents nested underneath it. When true, such
@@ -1485,7 +1565,27 @@ module Google
         #   nested immediately under the parent. Requests with `recursive` may not specify
         #   `show_missing`.
         # @param [Array<String>, String] request_options_request_tags
-        #   Optional. The request tags for the request.
+        #   Optional. The request tags for the request. Request tags are user-provided
+        #   strings used for usage monitoring, cost management, and observability. Callers
+        #   can associate custom application context (such as component, microservice,
+        #   feature name, or operation type) with database requests. These tags are
+        #   collected and aggregated in usage and monitoring reports, allowing billable
+        #   operations and usage metrics to be sliced and analyzed by tag. These tags *
+        #   only* show up in monitoring and are visible in administrative operations (such
+        #   as usage reports). They do not affect data storage, query semantics, or
+        #   request execution. Cardinality and Best Practices: - Request tags are most
+        #   effective when using a bounded set of distinct values (e.g., fewer than 100
+        #   distinct tags across an entire database). Using a large number of distinct
+        #   tags may result in tags being omitted from top usage dashboards. - Use
+        #   structured identifiers (for example: `app=cart`, `env=prod`, `service=checkout`
+        #   ) and avoid high-cardinality values such as UUIDs, request IDs, timestamps,
+        #   user IDs, or document keys. - Do not include sensitive data or personally
+        #   identifiable information (PII) in request tags, as they show up in
+        #   administrative monitoring. The tags are processed as follows: - Leading and
+        #   trailing whitespace is trimmed. - Empty tags (after trimming) are filtered out.
+        #   - Truncated to a maximum of 510 characters. - Deduplicated within the same
+        #   request. - Limited to a maximum of 50 tags per request (excess tags are
+        #   silently discarded).
         # @param [Boolean] show_missing
         #   If the list should show missing documents. A document is missing if it does
         #   not exist, but there are sub-documents nested underneath it. When true, such
@@ -1618,7 +1718,27 @@ module Google
         #   The list of field paths in the mask. See Document.fields for a field path
         #   syntax reference.
         # @param [Array<String>, String] request_options_request_tags
-        #   Optional. The request tags for the request.
+        #   Optional. The request tags for the request. Request tags are user-provided
+        #   strings used for usage monitoring, cost management, and observability. Callers
+        #   can associate custom application context (such as component, microservice,
+        #   feature name, or operation type) with database requests. These tags are
+        #   collected and aggregated in usage and monitoring reports, allowing billable
+        #   operations and usage metrics to be sliced and analyzed by tag. These tags *
+        #   only* show up in monitoring and are visible in administrative operations (such
+        #   as usage reports). They do not affect data storage, query semantics, or
+        #   request execution. Cardinality and Best Practices: - Request tags are most
+        #   effective when using a bounded set of distinct values (e.g., fewer than 100
+        #   distinct tags across an entire database). Using a large number of distinct
+        #   tags may result in tags being omitted from top usage dashboards. - Use
+        #   structured identifiers (for example: `app=cart`, `env=prod`, `service=checkout`
+        #   ) and avoid high-cardinality values such as UUIDs, request IDs, timestamps,
+        #   user IDs, or document keys. - Do not include sensitive data or personally
+        #   identifiable information (PII) in request tags, as they show up in
+        #   administrative monitoring. The tags are processed as follows: - Leading and
+        #   trailing whitespace is trimmed. - Empty tags (after trimming) are filtered out.
+        #   - Truncated to a maximum of 510 characters. - Deduplicated within the same
+        #   request. - Limited to a maximum of 50 tags per request (excess tags are
+        #   silently discarded).
         # @param [Array<String>, String] update_mask_field_paths
         #   The list of field paths in the mask. See Document.fields for a field path
         #   syntax reference.

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: google-apis-firestore_v1
 version: !ruby/object:Gem::Version
-  version: 0.98.0
+  version: 0.100.0
 platform: ruby
 authors:
 - Google LLC
@@ -57,7 +57,7 @@ licenses:
 metadata:
   bug_tracker_uri: https://github.com/googleapis/google-api-ruby-client/issues
   changelog_uri: https://github.com/googleapis/google-api-ruby-client/tree/main/generated/google-apis-firestore_v1/CHANGELOG.md
-  documentation_uri: https://googleapis.dev/ruby/google-apis-firestore_v1/v0.98.0
+  documentation_uri: https://googleapis.dev/ruby/google-apis-firestore_v1/v0.100.0
   source_code_uri: https://github.com/googleapis/google-api-ruby-client/tree/main/generated/google-apis-firestore_v1
 rdoc_options: []
 require_paths: