google-apis-retail_v2 0.126.0 → 0.127.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 58a0e1f7b419a6a18106b8812d7334b5f5bbef8759029c33fdba850801dd9aa5
-  data.tar.gz: 5797cf4c0beb42ce9da5b36f0ff6190ec46478904912f7adeb04a60fb4271595
+  metadata.gz: bc7c32e578018f4deae9c1de90f59e0a42cf3059e01c1f5eae090a1764404583
+  data.tar.gz: 04d43c88c0329ab0f4dd61549b8c6c02839d258d5d76b1bda58779a42ceafd54
 SHA512:
-  metadata.gz: 4638b5ccc70d132cb10a457952fce620c4243857967896d6ea56a56bf3159c5283c1d6e6c447336931d59118175de113eacd4926417e6f55b352d8324187ac49
-  data.tar.gz: ec7089a1f36a6b358da26f3586866c430b221341d82927b89d00ebba5f05c66faa8a60a1b353a570015b4560fbbd0c36d29f5c7ddd4f8a7360eaba34b2a5b0a6
+  metadata.gz: f0b41aec0ff8d0212fbe7ead89e5ac9cf39c6d68a59ac1c7a1b2dcce3683cd83415a49cd9777b5995665e41dff6e094017bf6b3cccd6291042bf8407fb582eb4
+  data.tar.gz: c7524353fdfcef9a3d3005380a4473263aa0e98d956336b3d8ef11370e1422a30e8368828dbc712fdb6fb33dfcce76f93ed891136009ead984609b019f94dd70

data/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Release history for google-apis-retail_v2
 
+### v0.127.0 (2026-03-01)
+
+* Regenerated from discovery document revision 20260219
+
 ### v0.126.0 (2026-02-08)
 
 * Regenerated from discovery document revision 20260129

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

@@ -1614,11 +1614,12 @@ module Google
       
         # Optional. The categories associated with a category page. Must be set for
         # category navigation queries to achieve good search quality. The format should
-        # be the same as UserEvent.page_categories; To represent full path of category,
-        # use '>' sign to separate different hierarchies. If '>' is part of the category
-        # name, replace it with other character(s). Category pages include special pages
-        # such as sales or promotions. For instance, a special sale page may have the
-        # category hierarchy: "pageCategories" : ["Sales > 2017 Black Friday Deals"].
+        # be the same as UserEvent.page_categories; To represent the full path of
+        # category, use the '>' sign, with one space on each side, to separate different
+        # hierarchies. If '>' is part of the category name, replace it with other
+        # character(s). Category pages include special pages such as sales or promotions.
+        # For instance, a special sale page may have the category hierarchy: "
+        # pageCategories" : ["Sales > 2017 Black Friday Deals"].
         # Corresponds to the JSON property `pageCategories`
         # @return [Array<String>]
         attr_accessor :page_categories
@@ -3942,20 +3943,20 @@ module Google
         # @return [Array<String>]
         attr_accessor :brands
       
-        # Product categories. This field is repeated for supporting one product
-        # belonging to several parallel categories. Strongly recommended using the full
-        # path for better search / recommendation quality. To represent full path of
-        # category, use '>' sign to separate different hierarchies. If '>' is part of
-        # the category name, replace it with other character(s). For example, if a shoes
-        # product belongs to both ["Shoes & Accessories" -> "Shoes"] and ["Sports &
-        # Fitness" -> "Athletic Clothing" -> "Shoes"], it could be represented as: "
-        # categories": [ "Shoes & Accessories > Shoes", "Sports & Fitness > Athletic
-        # Clothing > Shoes" ] Must be set for Type.PRIMARY Product otherwise an
-        # INVALID_ARGUMENT error is returned. At most 250 values are allowed per Product
-        # unless overridden through the Google Cloud console. Empty values are not
-        # allowed. Each value must be a UTF-8 encoded string with a length limit of 5,
-        # 000 characters. Otherwise, an INVALID_ARGUMENT error is returned.
-        # Corresponding properties: Google Merchant Center property
+        # Optional. Product categories. This field is repeated for supporting one
+        # product belonging to several parallel categories. Strongly recommended using
+        # the full path for better search / recommendation quality. To represent the
+        # full path of category, use the '>' sign, with one space on each side, to
+        # separate different hierarchies. If '>' is part of the category name, replace
+        # it with other character(s). For example, if a shoes product belongs to both ["
+        # Shoes & Accessories" -> "Shoes"] and ["Sports & Fitness" -> "Athletic Clothing"
+        # -> "Shoes"], it could be represented as: "categories": [ "Shoes & Accessories
+        # > Shoes", "Sports & Fitness > Athletic Clothing > Shoes" ] Must be set for
+        # Type.PRIMARY Product otherwise an INVALID_ARGUMENT error is returned. At most
+        # 250 values are allowed per Product unless overridden through the Google Cloud
+        # console. Empty values are not allowed. Each value must be a UTF-8 encoded
+        # string with a length limit of 5,000 characters. Otherwise, an INVALID_ARGUMENT
+        # error is returned. Corresponding properties: Google Merchant Center property
         # google_product_category. Schema.org property [Product.category] (https://
         # schema.org/category). [mc_google_product_category]: https://support.google.com/
         # merchants/answer/6324436
@@ -5657,13 +5658,14 @@ module Google
         # @return [String]
         attr_accessor :order_by
       
-        # The categories associated with a category page. Must be set for category
-        # navigation queries to achieve good search quality. The format should be the
-        # same as UserEvent.page_categories; To represent full path of category, use '>'
-        # sign to separate different hierarchies. If '>' is part of the category name,
-        # replace it with other character(s). Category pages include special pages such
-        # as sales or promotions. For instance, a special sale page may have the
-        # category hierarchy: "pageCategories" : ["Sales > 2017 Black Friday Deals"].
+        # Optional. The categories associated with a category page. Must be set for
+        # category navigation queries to achieve good search quality. The format should
+        # be the same as UserEvent.page_categories; To represent the full path of
+        # category, use '>' sign, with one space on each side, to separate different
+        # hierarchies. If '>' is part of the category name, replace it with other
+        # character(s). Category pages include special pages such as sales or promotions.
+        # For instance, a special sale page may have the category hierarchy: "
+        # pageCategories" : ["Sales > 2017 Black Friday Deals"].
         # Corresponds to the JSON property `pageCategories`
         # @return [Array<String>]
         attr_accessor :page_categories
@@ -7266,15 +7268,15 @@ module Google
         # @return [String]
         attr_accessor :order_by
       
-        # The categories associated with a category page. To represent full path of
-        # category, use '>' sign to separate different hierarchies. If '>' is part of
-        # the category name, replace it with other character(s). Category pages include
-        # special pages such as sales or promotions. For instance, a special sale page
-        # may have the category hierarchy: "pageCategories" : ["Sales > 2017 Black
-        # Friday Deals"]. Required for `category-page-view` events. At least one of
-        # search_query or page_categories is required for `search` events. Other event
-        # types should not set this field. Otherwise, an INVALID_ARGUMENT error is
-        # returned.
+        # Optional. The categories associated with a category page. To represent the
+        # full path of category, use the '>' sign, with one space on each side, to
+        # separate different hierarchies. If '>' is part of the category name, replace
+        # it with other character(s). Category pages include special pages such as sales
+        # or promotions. For instance, a special sale page may have the category
+        # hierarchy: "pageCategories" : ["Sales > 2017 Black Friday Deals"]. Required
+        # for `category-page-view` events. At least one of search_query or
+        # page_categories is required for `search` events. Other event types should not
+        # set this field. Otherwise, an INVALID_ARGUMENT error is returned.
         # Corresponds to the JSON property `pageCategories`
         # @return [Array<String>]
         attr_accessor :page_categories

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

@@ -16,13 +16,13 @@ module Google
   module Apis
     module RetailV2
       # Version of the google-apis-retail_v2 gem
-      GEM_VERSION = "0.126.0"
+      GEM_VERSION = "0.127.0"
 
       # Version of the code generator used to generate this client
       GENERATOR_VERSION = "0.18.0"
 
       # Revision of the discovery document this client was generated from
-      REVISION = "20260129"
+      REVISION = "20260219"
     end
   end
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: google-apis-retail_v2
 version: !ruby/object:Gem::Version
-  version: 0.126.0
+  version: 0.127.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-retail_v2/CHANGELOG.md
-  documentation_uri: https://googleapis.dev/ruby/google-apis-retail_v2/v0.126.0
+  documentation_uri: https://googleapis.dev/ruby/google-apis-retail_v2/v0.127.0
   source_code_uri: https://github.com/googleapis/google-api-ruby-client/tree/main/generated/google-apis-retail_v2
 rdoc_options: []
 require_paths: