google-apis-retail_v2alpha 0.133.0 → 0.134.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 0762ccca8e15042c447341d266a44883ede4a3d7148512cb2ce92a84bb1ffdbf
-  data.tar.gz: 13c7efb39233dc797dc1bbd9a225d2fe1f7882cee9b70455ea688653b8ecc5b5
+  metadata.gz: 258fb98bb270ecfb1a626fcbc0ad1c92c0ac9cbf7ee652f7f2e41f554b7f62b7
+  data.tar.gz: 57b39be706c71f80c2368c52171b73fe82115d6302f8828bef0ccb044566099f
 SHA512:
-  metadata.gz: 8db4822f338e01bb4788bef357496f63bdc5b39213049c4c14181500a447076dc56541d92b8065db2e135290b91bbb87fe7b03550db67403a638566a05bba679
-  data.tar.gz: f7d9efb48c8220a761b581a50b38afa33c27af5666676fc94b7a4a94b4193588c2473a1d3b3647944866c66235aad0fc51f142b3c1f13b7c905269e183f98f5b
+  metadata.gz: 7c8f5f4e25cedb635d9fc768f6c10fad81e59b76862b13466a77e949695623ceab95bea5ead0f556807e43a31b8d3da13bde115af1f5f637aa3fa4cbd4f55350
+  data.tar.gz: 8fe8cd19849f4a7c3140b07fd237cb2282f8bb89bd6cabd37798aacce1bb532a864b6905d76627f11269c6af8742e60778e83a105291371d51172b711618d1ba

data/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Release history for google-apis-retail_v2alpha
 
+### v0.134.0 (2026-03-15)
+
+* Regenerated from discovery document revision 20260219
+
 ### v0.133.0 (2026-02-08)
 
 * Regenerated from discovery document revision 20260129

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

@@ -2832,11 +2832,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
@@ -5905,20 +5906,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
@@ -7651,13 +7652,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
@@ -9296,15 +9298,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_v2alpha/gem_version.rb

@@ -16,13 +16,13 @@ module Google
   module Apis
     module RetailV2alpha
       # Version of the google-apis-retail_v2alpha gem
-      GEM_VERSION = "0.133.0"
+      GEM_VERSION = "0.134.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_v2alpha
 version: !ruby/object:Gem::Version
-  version: 0.133.0
+  version: 0.134.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_v2alpha/CHANGELOG.md
-  documentation_uri: https://googleapis.dev/ruby/google-apis-retail_v2alpha/v0.133.0
+  documentation_uri: https://googleapis.dev/ruby/google-apis-retail_v2alpha/v0.134.0
   source_code_uri: https://github.com/googleapis/google-api-ruby-client/tree/main/generated/google-apis-retail_v2alpha
 rdoc_options: []
 require_paths: