google-apis-chat_v1 0.68.0 → 0.70.0

Sign up to get free protection for your applications and to get access to all the features.
Files changed (6) hide show
  1. checksums.yaml +4 -4
  2. data/CHANGELOG.md +8 -0
  3. data/lib/google/apis/chat_v1/classes.rb +152 -140
  4. data/lib/google/apis/chat_v1/gem_version.rb +2 -2
  5. data/lib/google/apis/chat_v1/service.rb +42 -66
  6. metadata +4 -4
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 5612946e363951d77cf43c85a687c12b56869136c97a6298a704e866acb251cc
4
- data.tar.gz: 2888c3afc13c516435eb4d3f5551463b910a85d93aa967e9d118b854ab16cd93
3
+ metadata.gz: f83ed9bbbeed1bd7a0f49fcc932201d577911c51be0f5b8450ce454990dfd57b
4
+ data.tar.gz: d45ba15dc2fd0c474aa1abd8971a8736790d2819afbe7e3f8b27f9a95ec35361
5
5
  SHA512:
6
- metadata.gz: 04d84e3f5dde32844dd849f33a8c5c94ff9626dfccdbd157cfac4c54eb9cd717e928eb3e0a1b4153fb3e75393e9318accc682eb2137be1fb1d86508fd4ca1286
7
- data.tar.gz: 453ece9fe07a69b08380809694e86879c233fe2391152eea3c06b67fc5748ee0dba0b987b2a87bb919b4b999dc2cf7de3299832ed507f7eb9724d46f952db368
6
+ metadata.gz: 528643c9f0bf5ff9c5d21a5637163522098a853ca5a63eb077218d9a39905832389b0871be402662378d21a914ec1cfee710ac88a6111141bb249ecd425e2213
7
+ data.tar.gz: 92aa0621c15f3f5ee1cad75fec64629673d1f69f5e837f5067123ae31f2e4c9af3a0588845bb3b019544bca2763b343202040f707b8699f331e41ca6a867bd36
data/CHANGELOG.md CHANGED
@@ -1,5 +1,13 @@
1
1
  # Release history for google-apis-chat_v1
2
2
 
3
+ ### v0.70.0 (2023-09-03)
4
+
5
+ * Regenerated from discovery document revision 20230827
6
+
7
+ ### v0.69.0 (2023-08-27)
8
+
9
+ * Regenerated from discovery document revision 20230822
10
+
3
11
  ### v0.68.0 (2023-08-13)
4
12
 
5
13
  * Regenerated from discovery document revision 20230806
data/lib/google/apis/chat_v1/classes.rb CHANGED
@@ -110,12 +110,14 @@ module Google
110
110
  end
111
111
  end
112
112
 
113
- # Annotations associated with the plain-text body of the message. Example plain-
114
- # text message body: ``` Hello @FooBot how are you!" ``` The corresponding
115
- # annotations metadata: ``` "annotations":[` "type":"USER_MENTION", "startIndex":
116
- # 6, "length":7, "userMention": ` "user": ` "name":"users/`user`", "displayName":
117
- # "FooBot", "avatarUrl":"https://goo.gl/aeDtrS", "type":"BOT" `, "type":"MENTION"
118
- # ` `] ```
113
+ # Output only. Annotations associated with the plain-text body of the message.
114
+ # To add basic formatting to a text message, see [Format text messages](https://
115
+ # developers.google.com/chat/api/guides/message-formats/text#format-texts).
116
+ # Example plain-text message body: ``` Hello @FooBot how are you!" ``` The
117
+ # corresponding annotations metadata: ``` "annotations":[` "type":"USER_MENTION",
118
+ # "startIndex":6, "length":7, "userMention": ` "user": ` "name":"users/`user`",
119
+ # "displayName":"FooBot", "avatarUrl":"https://goo.gl/aeDtrS", "type":"BOT" `, "
120
+ # type":"MENTION" ` `] ```
119
121
  class Annotation
120
122
  include Google::Apis::Core::Hashable
121
123
 
@@ -402,41 +404,42 @@ module Google
402
404
  end
403
405
  end
404
406
 
405
- # Widgets for Chat apps to specify.
407
+ # A [card](https://developers.google.com/chat/api/reference/rest/v1/cards) in a
408
+ # Google Chat message. Only Chat apps can create cards. If your Chat app [
409
+ # authenticates as a user](https://developers.google.com/chat/api/guides/auth/
410
+ # users), the message can't contain cards.
406
411
  class CardWithId
407
412
  include Google::Apis::Core::Hashable
408
413
 
409
- # Cards support a defined layout, interactive UI elements like buttons, and rich
410
- # media like images. Use cards to present detailed information, gather
411
- # information from users, and guide users to take a next step. In Google Chat,
412
- # cards appear in several places: - As stand-alone messages. - Accompanying a
413
- # text message, just beneath the text message. - As a [dialog](https://
414
- # developers.google.com/chat/how-tos/dialogs). The following example JSON
415
- # creates a "contact card" that features: - A header with the contact's name,
416
- # job title, and avatar picture. - A section with the contact information,
417
- # including formatted text. - Buttons that users can click to share the contact,
418
- # or see more or less information. For more examples, see [Design dynamic,
419
- # interactive, and consistent UIs with cards](https://developers.google.com/chat/
420
- # ui). ![Example contact card](https://developers.google.com/chat/images/
421
- # card_api_reference.png) ``` ` "cardsV2": [ ` "cardId": "unique-card-id", "card"
422
- # : ` "header": ` "title": "Sasha", "subtitle": "Software Engineer", "imageUrl":
423
- # "https://developers.google.com/chat/images/quickstart-app-avatar.png", "
424
- # imageType": "CIRCLE", "imageAltText": "Avatar for Sasha", `, "sections": [ ` "
425
- # header": "Contact Info", "collapsible": true, "uncollapsibleWidgetsCount": 1, "
426
- # widgets": [ ` "decoratedText": ` "startIcon": ` "knownIcon": "EMAIL", `, "text"
427
- # : "sasha@example.com", ` `, ` "decoratedText": ` "startIcon": ` "knownIcon": "
428
- # PERSON", `, "text": "Online", `, `, ` "decoratedText": ` "startIcon": ` "
429
- # knownIcon": "PHONE", `, "text": "+1 (555) 555-1234", ` `, ` "buttonList": ` "
430
- # buttons": [ ` "text": "Share", "onClick": ` "openLink": ` "url": "https://
431
- # example.com/share", ` ` `, ` "text": "Edit", "onClick": ` "action": ` "
432
- # function": "goToView", "parameters": [ ` "key": "viewType", "value": "EDIT", `
433
- # ], ` ` `, ], ` `, ], `, ], `, ` ], ` ```
414
+ # A card interface displayed in a Google Chat message or Google Workspace Add-on.
415
+ # Cards support a defined layout, interactive UI elements like buttons, and
416
+ # rich media like images. Use cards to present detailed information, gather
417
+ # information from users, and guide users to take a next step. To learn how to
418
+ # build cards, see the following documentation: * For Google Chat apps, see [
419
+ # Design dynamic, interactive, and consistent UIs with cards](https://developers.
420
+ # google.com/chat/ui). * For Google Workspace Add-ons, see [Card-based
421
+ # interfaces](https://developers.google.com/apps-script/add-ons/concepts/cards).
422
+ # **Example: Card message for a Google Chat app** ![Example contact card](https:/
423
+ # /developers.google.com/chat/images/card_api_reference.png) To create the
424
+ # sample card message in Google Chat, use the following JSON: ``` ` "cardsV2": [
425
+ # ` "cardId": "unique-card-id", "card": ` "header": ` "title": "Sasha", "
426
+ # subtitle": "Software Engineer", "imageUrl": "https://developers.google.com/
427
+ # chat/images/quickstart-app-avatar.png", "imageType": "CIRCLE", "imageAltText":
428
+ # "Avatar for Sasha", `, "sections": [ ` "header": "Contact Info", "collapsible":
429
+ # true, "uncollapsibleWidgetsCount": 1, "widgets": [ ` "decoratedText": ` "
430
+ # startIcon": ` "knownIcon": "EMAIL", `, "text": "sasha@example.com", ` `, ` "
431
+ # decoratedText": ` "startIcon": ` "knownIcon": "PERSON", `, "text": "Online", `,
432
+ # `, ` "decoratedText": ` "startIcon": ` "knownIcon": "PHONE", `, "text": "+1 (
433
+ # 555) 555-1234", ` `, ` "buttonList": ` "buttons": [ ` "text": "Share", "
434
+ # onClick": ` "openLink": ` "url": "https://example.com/share", ` ` `, ` "text":
435
+ # "Edit", "onClick": ` "action": ` "function": "goToView", "parameters": [ ` "
436
+ # key": "viewType", "value": "EDIT", ` ], ` ` `, ], ` `, ], `, ], `, ` ], ` ```
434
437
  # Corresponds to the JSON property `card`
435
438
  # @return [Google::Apis::ChatV1::GoogleAppsCardV1Card]
436
439
  attr_accessor :card
437
440
 
438
- # Required for `cardsV2` messages. Chat app-specified identifier for this widget.
439
- # Scoped within a message.
441
+ # Required if the message contains multiple cards. A unique identifier for a
442
+ # card in a message.
440
443
  # Corresponds to the JSON property `cardId`
441
444
  # @return [String]
442
445
  attr_accessor :card_id
@@ -768,9 +771,12 @@ module Google
768
771
  end
769
772
  end
770
773
 
771
- # Google Chat events. To learn how to use events, see [Receive and respond to
772
- # Google Chat events](https://developers.google.com/chat/api/guides/message-
773
- # formats).
774
+ # A Google Chat app interaction event. To learn about interaction events, see [
775
+ # Receive and respond to interactions with your Google Chat app](https://
776
+ # developers.google.com/chat/api/guides/message-formats). To learn about event
777
+ # types and for example event payloads, see [Types of Google Chat app
778
+ # interaction events](https://developers.google.com/chat/api/guides/message-
779
+ # formats/events).
774
780
  class DeprecatedEvent
775
781
  include Google::Apis::Core::Hashable
776
782
 
@@ -796,25 +802,25 @@ module Google
796
802
  # @return [String]
797
803
  attr_accessor :config_complete_redirect_url
798
804
 
799
- # The type of [dialog](https://developers.google.com/chat/how-tos/dialogs) event
800
- # received.
805
+ # The type of [dialog](https://developers.google.com/chat/how-tos/dialogs)
806
+ # interaction event received.
801
807
  # Corresponds to the JSON property `dialogEventType`
802
808
  # @return [String]
803
809
  attr_accessor :dialog_event_type
804
810
 
805
- # The timestamp indicating when the event occurred.
811
+ # The timestamp indicating when the interaction event occurred.
806
812
  # Corresponds to the JSON property `eventTime`
807
813
  # @return [String]
808
814
  attr_accessor :event_time
809
815
 
810
- # True when the event is related to [dialogs](https://developers.google.com/chat/
811
- # how-tos/dialogs).
816
+ # For `CARD_CLICKED` interaction events, whether the user interacted with a [
817
+ # dialog](https://developers.google.com/chat/how-tos/dialogs).
812
818
  # Corresponds to the JSON property `isDialogEvent`
813
819
  # @return [Boolean]
814
820
  attr_accessor :is_dialog_event
815
821
  alias_method :is_dialog_event?, :is_dialog_event
816
822
 
817
- # A message in Google Chat.
823
+ # A message in a Google Chat space.
818
824
  # Corresponds to the JSON property `message`
819
825
  # @return [Google::Apis::ChatV1::Message]
820
826
  attr_accessor :message
@@ -825,9 +831,9 @@ module Google
825
831
  # @return [Google::Apis::ChatV1::Space]
826
832
  attr_accessor :space
827
833
 
828
- # The Chat app-defined key for the thread related to the event. See [`spaces.
829
- # messages.thread.threadKey`](/chat/api/reference/rest/v1/spaces.messages#Thread.
830
- # FIELDS.thread_key) for more information.
834
+ # The Chat app-defined key for the thread related to the interaction event. See [
835
+ # `spaces.messages.thread.threadKey`](/chat/api/reference/rest/v1/spaces.
836
+ # messages#Thread.FIELDS.thread_key) for more information.
831
837
  # Corresponds to the JSON property `threadKey`
832
838
  # @return [String]
833
839
  attr_accessor :thread_key
@@ -843,7 +849,9 @@ module Google
843
849
  # @return [String]
844
850
  attr_accessor :token
845
851
 
846
- # The type of the event.
852
+ # The type of interaction event. For details, see [Types of Google Chat app
853
+ # interaction events](https://developers.google.com/chat/api/guides/message-
854
+ # formats/events).
847
855
  # Corresponds to the JSON property `type`
848
856
  # @return [String]
849
857
  attr_accessor :type
@@ -881,31 +889,29 @@ module Google
881
889
  class Dialog
882
890
  include Google::Apis::Core::Hashable
883
891
 
884
- # Cards support a defined layout, interactive UI elements like buttons, and rich
885
- # media like images. Use cards to present detailed information, gather
886
- # information from users, and guide users to take a next step. In Google Chat,
887
- # cards appear in several places: - As stand-alone messages. - Accompanying a
888
- # text message, just beneath the text message. - As a [dialog](https://
889
- # developers.google.com/chat/how-tos/dialogs). The following example JSON
890
- # creates a "contact card" that features: - A header with the contact's name,
891
- # job title, and avatar picture. - A section with the contact information,
892
- # including formatted text. - Buttons that users can click to share the contact,
893
- # or see more or less information. For more examples, see [Design dynamic,
894
- # interactive, and consistent UIs with cards](https://developers.google.com/chat/
895
- # ui). ![Example contact card](https://developers.google.com/chat/images/
896
- # card_api_reference.png) ``` ` "cardsV2": [ ` "cardId": "unique-card-id", "card"
897
- # : ` "header": ` "title": "Sasha", "subtitle": "Software Engineer", "imageUrl":
898
- # "https://developers.google.com/chat/images/quickstart-app-avatar.png", "
899
- # imageType": "CIRCLE", "imageAltText": "Avatar for Sasha", `, "sections": [ ` "
900
- # header": "Contact Info", "collapsible": true, "uncollapsibleWidgetsCount": 1, "
901
- # widgets": [ ` "decoratedText": ` "startIcon": ` "knownIcon": "EMAIL", `, "text"
902
- # : "sasha@example.com", ` `, ` "decoratedText": ` "startIcon": ` "knownIcon": "
903
- # PERSON", `, "text": "Online", `, `, ` "decoratedText": ` "startIcon": ` "
904
- # knownIcon": "PHONE", `, "text": "+1 (555) 555-1234", ` `, ` "buttonList": ` "
905
- # buttons": [ ` "text": "Share", "onClick": ` "openLink": ` "url": "https://
906
- # example.com/share", ` ` `, ` "text": "Edit", "onClick": ` "action": ` "
907
- # function": "goToView", "parameters": [ ` "key": "viewType", "value": "EDIT", `
908
- # ], ` ` `, ], ` `, ], `, ], `, ` ], ` ```
892
+ # A card interface displayed in a Google Chat message or Google Workspace Add-on.
893
+ # Cards support a defined layout, interactive UI elements like buttons, and
894
+ # rich media like images. Use cards to present detailed information, gather
895
+ # information from users, and guide users to take a next step. To learn how to
896
+ # build cards, see the following documentation: * For Google Chat apps, see [
897
+ # Design dynamic, interactive, and consistent UIs with cards](https://developers.
898
+ # google.com/chat/ui). * For Google Workspace Add-ons, see [Card-based
899
+ # interfaces](https://developers.google.com/apps-script/add-ons/concepts/cards).
900
+ # **Example: Card message for a Google Chat app** ![Example contact card](https:/
901
+ # /developers.google.com/chat/images/card_api_reference.png) To create the
902
+ # sample card message in Google Chat, use the following JSON: ``` ` "cardsV2": [
903
+ # ` "cardId": "unique-card-id", "card": ` "header": ` "title": "Sasha", "
904
+ # subtitle": "Software Engineer", "imageUrl": "https://developers.google.com/
905
+ # chat/images/quickstart-app-avatar.png", "imageType": "CIRCLE", "imageAltText":
906
+ # "Avatar for Sasha", `, "sections": [ ` "header": "Contact Info", "collapsible":
907
+ # true, "uncollapsibleWidgetsCount": 1, "widgets": [ ` "decoratedText": ` "
908
+ # startIcon": ` "knownIcon": "EMAIL", `, "text": "sasha@example.com", ` `, ` "
909
+ # decoratedText": ` "startIcon": ` "knownIcon": "PERSON", `, "text": "Online", `,
910
+ # `, ` "decoratedText": ` "startIcon": ` "knownIcon": "PHONE", `, "text": "+1 (
911
+ # 555) 555-1234", ` `, ` "buttonList": ` "buttons": [ ` "text": "Share", "
912
+ # onClick": ` "openLink": ` "url": "https://example.com/share", ` ` `, ` "text":
913
+ # "Edit", "onClick": ` "action": ` "function": "goToView", "parameters": [ ` "
914
+ # key": "viewType", "value": "EDIT", ` ], ` ` `, ], ` `, ], `, ], `, ` ], ` ```
909
915
  # Corresponds to the JSON property `body`
910
916
  # @return [Google::Apis::ChatV1::GoogleAppsCardV1Card]
911
917
  attr_accessor :body
@@ -1364,31 +1370,29 @@ module Google
1364
1370
  end
1365
1371
  end
1366
1372
 
1367
- # Cards support a defined layout, interactive UI elements like buttons, and rich
1368
- # media like images. Use cards to present detailed information, gather
1369
- # information from users, and guide users to take a next step. In Google Chat,
1370
- # cards appear in several places: - As stand-alone messages. - Accompanying a
1371
- # text message, just beneath the text message. - As a [dialog](https://
1372
- # developers.google.com/chat/how-tos/dialogs). The following example JSON
1373
- # creates a "contact card" that features: - A header with the contact's name,
1374
- # job title, and avatar picture. - A section with the contact information,
1375
- # including formatted text. - Buttons that users can click to share the contact,
1376
- # or see more or less information. For more examples, see [Design dynamic,
1377
- # interactive, and consistent UIs with cards](https://developers.google.com/chat/
1378
- # ui). ![Example contact card](https://developers.google.com/chat/images/
1379
- # card_api_reference.png) ``` ` "cardsV2": [ ` "cardId": "unique-card-id", "card"
1380
- # : ` "header": ` "title": "Sasha", "subtitle": "Software Engineer", "imageUrl":
1381
- # "https://developers.google.com/chat/images/quickstart-app-avatar.png", "
1382
- # imageType": "CIRCLE", "imageAltText": "Avatar for Sasha", `, "sections": [ ` "
1383
- # header": "Contact Info", "collapsible": true, "uncollapsibleWidgetsCount": 1, "
1384
- # widgets": [ ` "decoratedText": ` "startIcon": ` "knownIcon": "EMAIL", `, "text"
1385
- # : "sasha@example.com", ` `, ` "decoratedText": ` "startIcon": ` "knownIcon": "
1386
- # PERSON", `, "text": "Online", `, `, ` "decoratedText": ` "startIcon": ` "
1387
- # knownIcon": "PHONE", `, "text": "+1 (555) 555-1234", ` `, ` "buttonList": ` "
1388
- # buttons": [ ` "text": "Share", "onClick": ` "openLink": ` "url": "https://
1389
- # example.com/share", ` ` `, ` "text": "Edit", "onClick": ` "action": ` "
1390
- # function": "goToView", "parameters": [ ` "key": "viewType", "value": "EDIT", `
1391
- # ], ` ` `, ], ` `, ], `, ], `, ` ], ` ```
1373
+ # A card interface displayed in a Google Chat message or Google Workspace Add-on.
1374
+ # Cards support a defined layout, interactive UI elements like buttons, and
1375
+ # rich media like images. Use cards to present detailed information, gather
1376
+ # information from users, and guide users to take a next step. To learn how to
1377
+ # build cards, see the following documentation: * For Google Chat apps, see [
1378
+ # Design dynamic, interactive, and consistent UIs with cards](https://developers.
1379
+ # google.com/chat/ui). * For Google Workspace Add-ons, see [Card-based
1380
+ # interfaces](https://developers.google.com/apps-script/add-ons/concepts/cards).
1381
+ # **Example: Card message for a Google Chat app** ![Example contact card](https:/
1382
+ # /developers.google.com/chat/images/card_api_reference.png) To create the
1383
+ # sample card message in Google Chat, use the following JSON: ``` ` "cardsV2": [
1384
+ # ` "cardId": "unique-card-id", "card": ` "header": ` "title": "Sasha", "
1385
+ # subtitle": "Software Engineer", "imageUrl": "https://developers.google.com/
1386
+ # chat/images/quickstart-app-avatar.png", "imageType": "CIRCLE", "imageAltText":
1387
+ # "Avatar for Sasha", `, "sections": [ ` "header": "Contact Info", "collapsible":
1388
+ # true, "uncollapsibleWidgetsCount": 1, "widgets": [ ` "decoratedText": ` "
1389
+ # startIcon": ` "knownIcon": "EMAIL", `, "text": "sasha@example.com", ` `, ` "
1390
+ # decoratedText": ` "startIcon": ` "knownIcon": "PERSON", `, "text": "Online", `,
1391
+ # `, ` "decoratedText": ` "startIcon": ` "knownIcon": "PHONE", `, "text": "+1 (
1392
+ # 555) 555-1234", ` `, ` "buttonList": ` "buttons": [ ` "text": "Share", "
1393
+ # onClick": ` "openLink": ` "url": "https://example.com/share", ` ` `, ` "text":
1394
+ # "Edit", "onClick": ` "action": ` "function": "goToView", "parameters": [ ` "
1395
+ # key": "viewType", "value": "EDIT", ` ], ` ` `, ], ` `, ], `, ], `, ` ], ` ```
1392
1396
  class GoogleAppsCardV1Card
1393
1397
  include Google::Apis::Core::Hashable
1394
1398
 
@@ -2112,31 +2116,29 @@ module Google
2112
2116
  # @return [Google::Apis::ChatV1::GoogleAppsCardV1Action]
2113
2117
  attr_accessor :action
2114
2118
 
2115
- # Cards support a defined layout, interactive UI elements like buttons, and rich
2116
- # media like images. Use cards to present detailed information, gather
2117
- # information from users, and guide users to take a next step. In Google Chat,
2118
- # cards appear in several places: - As stand-alone messages. - Accompanying a
2119
- # text message, just beneath the text message. - As a [dialog](https://
2120
- # developers.google.com/chat/how-tos/dialogs). The following example JSON
2121
- # creates a "contact card" that features: - A header with the contact's name,
2122
- # job title, and avatar picture. - A section with the contact information,
2123
- # including formatted text. - Buttons that users can click to share the contact,
2124
- # or see more or less information. For more examples, see [Design dynamic,
2125
- # interactive, and consistent UIs with cards](https://developers.google.com/chat/
2126
- # ui). ![Example contact card](https://developers.google.com/chat/images/
2127
- # card_api_reference.png) ``` ` "cardsV2": [ ` "cardId": "unique-card-id", "card"
2128
- # : ` "header": ` "title": "Sasha", "subtitle": "Software Engineer", "imageUrl":
2129
- # "https://developers.google.com/chat/images/quickstart-app-avatar.png", "
2130
- # imageType": "CIRCLE", "imageAltText": "Avatar for Sasha", `, "sections": [ ` "
2131
- # header": "Contact Info", "collapsible": true, "uncollapsibleWidgetsCount": 1, "
2132
- # widgets": [ ` "decoratedText": ` "startIcon": ` "knownIcon": "EMAIL", `, "text"
2133
- # : "sasha@example.com", ` `, ` "decoratedText": ` "startIcon": ` "knownIcon": "
2134
- # PERSON", `, "text": "Online", `, `, ` "decoratedText": ` "startIcon": ` "
2135
- # knownIcon": "PHONE", `, "text": "+1 (555) 555-1234", ` `, ` "buttonList": ` "
2136
- # buttons": [ ` "text": "Share", "onClick": ` "openLink": ` "url": "https://
2137
- # example.com/share", ` ` `, ` "text": "Edit", "onClick": ` "action": ` "
2138
- # function": "goToView", "parameters": [ ` "key": "viewType", "value": "EDIT", `
2139
- # ], ` ` `, ], ` `, ], `, ], `, ` ], ` ```
2119
+ # A card interface displayed in a Google Chat message or Google Workspace Add-on.
2120
+ # Cards support a defined layout, interactive UI elements like buttons, and
2121
+ # rich media like images. Use cards to present detailed information, gather
2122
+ # information from users, and guide users to take a next step. To learn how to
2123
+ # build cards, see the following documentation: * For Google Chat apps, see [
2124
+ # Design dynamic, interactive, and consistent UIs with cards](https://developers.
2125
+ # google.com/chat/ui). * For Google Workspace Add-ons, see [Card-based
2126
+ # interfaces](https://developers.google.com/apps-script/add-ons/concepts/cards).
2127
+ # **Example: Card message for a Google Chat app** ![Example contact card](https:/
2128
+ # /developers.google.com/chat/images/card_api_reference.png) To create the
2129
+ # sample card message in Google Chat, use the following JSON: ``` ` "cardsV2": [
2130
+ # ` "cardId": "unique-card-id", "card": ` "header": ` "title": "Sasha", "
2131
+ # subtitle": "Software Engineer", "imageUrl": "https://developers.google.com/
2132
+ # chat/images/quickstart-app-avatar.png", "imageType": "CIRCLE", "imageAltText":
2133
+ # "Avatar for Sasha", `, "sections": [ ` "header": "Contact Info", "collapsible":
2134
+ # true, "uncollapsibleWidgetsCount": 1, "widgets": [ ` "decoratedText": ` "
2135
+ # startIcon": ` "knownIcon": "EMAIL", `, "text": "sasha@example.com", ` `, ` "
2136
+ # decoratedText": ` "startIcon": ` "knownIcon": "PERSON", `, "text": "Online", `,
2137
+ # `, ` "decoratedText": ` "startIcon": ` "knownIcon": "PHONE", `, "text": "+1 (
2138
+ # 555) 555-1234", ` `, ` "buttonList": ` "buttons": [ ` "text": "Share", "
2139
+ # onClick": ` "openLink": ` "url": "https://example.com/share", ` ` `, ` "text":
2140
+ # "Edit", "onClick": ` "action": ` "function": "goToView", "parameters": [ ` "
2141
+ # key": "viewType", "value": "EDIT", ` ], ` ` `, ], ` `, ], `, ], `, ` ], ` ```
2140
2142
  # Corresponds to the JSON property `card`
2141
2143
  # @return [Google::Apis::ChatV1::GoogleAppsCardV1Card]
2142
2144
  attr_accessor :card
@@ -2971,7 +2973,9 @@ module Google
2971
2973
  end
2972
2974
  end
2973
2975
 
2974
- # Types of data inputs for widgets. Users enter data with these inputs.
2976
+ # Types of data that users can enter on cards or dialogs. To learn how to
2977
+ # process information from users, see [Read form data input by users on cards](
2978
+ # https://developers.google.com/chat/ui/read-form-data).
2975
2979
  class Inputs
2976
2980
  include Google::Apis::Core::Hashable
2977
2981
 
@@ -3280,7 +3284,7 @@ module Google
3280
3284
  end
3281
3285
  end
3282
3286
 
3283
- # A message in Google Chat.
3287
+ # A message in a Google Chat space.
3284
3288
  class Message
3285
3289
  include Google::Apis::Core::Hashable
3286
3290
 
@@ -3318,15 +3322,12 @@ module Google
3318
3322
  # @return [Array<Google::Apis::ChatV1::Card>]
3319
3323
  attr_accessor :cards
3320
3324
 
3321
- # Richly formatted and interactive cards that display UI elements and editable
3322
- # widgets, such as: - Formatted text - Buttons - Clickable images - Checkboxes -
3323
- # Radio buttons - Input widgets. Cards are usually displayed below the text body
3324
- # of a Chat message, but can situationally appear other places, such as [dialogs]
3325
- # (https://developers.google.com/chat/how-tos/dialogs). Each card can have a
3326
- # maximum size of 32 KB. The `cardId` is a unique identifier among cards in the
3327
- # same message and for identifying user input values. Currently supported
3328
- # widgets include: - `TextParagraph` - `DecoratedText` - `Image` - `ButtonList` -
3329
- # `Divider` - `TextInput` - `SelectionInput` - `Grid`
3325
+ # An array of [cards](https://developers.google.com/chat/api/reference/rest/v1/
3326
+ # cards). Only Chat apps can create cards. If your Chat app [authenticates as a
3327
+ # user](https://developers.google.com/chat/api/guides/auth/users), the messages
3328
+ # can't contain cards. To learn about cards and how to create them, see [Design
3329
+ # dynamic, interactive, and consistent UIs with cards](https://developers.google.
3330
+ # com/chat/ui).
3330
3331
  # Corresponds to the JSON property `cardsV2`
3331
3332
  # @return [Array<Google::Apis::ChatV1::CardWithId>]
3332
3333
  attr_accessor :cards_v2
@@ -3433,8 +3434,11 @@ module Google
3433
3434
  attr_accessor :text
3434
3435
 
3435
3436
  # A thread in a Google Chat space. For example usage, see [Start or reply to a
3436
- # message thread](https://developers.google.com/chat/api/guides/crudl/messages#
3437
- # start_or_reply_to_a_message_thread).
3437
+ # message thread](https://developers.google.com/chat/api/guides/v1/messages/
3438
+ # create#create-message-thread). If you specify a thread when creating a message,
3439
+ # you can set the [`messageReplyOption`](https://developers.google.com/chat/api/
3440
+ # reference/rest/v1/spaces.messages/create#messagereplyoption) field to
3441
+ # determine what happens if no matching thread is found.
3438
3442
  # Corresponds to the JSON property `thread`
3439
3443
  # @return [Google::Apis::ChatV1::Thread]
3440
3444
  attr_accessor :thread
@@ -3995,18 +3999,26 @@ module Google
3995
3999
  end
3996
4000
 
3997
4001
  # A thread in a Google Chat space. For example usage, see [Start or reply to a
3998
- # message thread](https://developers.google.com/chat/api/guides/crudl/messages#
3999
- # start_or_reply_to_a_message_thread).
4002
+ # message thread](https://developers.google.com/chat/api/guides/v1/messages/
4003
+ # create#create-message-thread). If you specify a thread when creating a message,
4004
+ # you can set the [`messageReplyOption`](https://developers.google.com/chat/api/
4005
+ # reference/rest/v1/spaces.messages/create#messagereplyoption) field to
4006
+ # determine what happens if no matching thread is found.
4000
4007
  class Thread
4001
4008
  include Google::Apis::Core::Hashable
4002
4009
 
4003
- # Resource name of the thread. Example: `spaces/`space`/threads/`thread``
4010
+ # Output only. Resource name of the thread. Example: `spaces/`space`/threads/`
4011
+ # thread``
4004
4012
  # Corresponds to the JSON property `name`
4005
4013
  # @return [String]
4006
4014
  attr_accessor :name
4007
4015
 
4008
- # Optional. ID for the thread. Supports up to 4000 characters. Input for
4009
- # creating or updating a thread. Otherwise, output only.
4016
+ # Optional. Input for creating or updating a thread. Otherwise, output only. ID
4017
+ # for the thread. Supports up to 4000 characters. This ID is unique to the Chat
4018
+ # app that sets it. For example, if multiple Chat apps create a message using
4019
+ # the same thread key, the messages are posted in different threads. To reply in
4020
+ # a thread created by a person or another Chat app, specify the thread `name`
4021
+ # field instead.
4010
4022
  # Corresponds to the JSON property `threadKey`
4011
4023
  # @return [String]
4012
4024
  attr_accessor :thread_key
data/lib/google/apis/chat_v1/gem_version.rb CHANGED
@@ -16,13 +16,13 @@ module Google
16
16
  module Apis
17
17
  module ChatV1
18
18
  # Version of the google-apis-chat_v1 gem
19
- GEM_VERSION = "0.68.0"
19
+ GEM_VERSION = "0.70.0"
20
20
 
21
21
  # Version of the code generator used to generate this client
22
22
  GENERATOR_VERSION = "0.12.0"
23
23
 
24
24
  # Revision of the discovery document this client was generated from
25
- REVISION = "20230806"
25
+ REVISION = "20230827"
26
26
  end
27
27
  end
28
28
  end
data/lib/google/apis/chat_v1/service.rb CHANGED
@@ -91,9 +91,8 @@ module Google
91
91
  # Uploads an attachment. For an example, see [Upload media as a file attachment](
92
92
  # https://developers.google.com/chat/api/guides/v1/media-and-attachments/upload).
93
93
  # Requires user [authentication](https://developers.google.com/chat/api/guides/
94
- # auth/users) and the `chat.messages` or `chat.messages.create` authorization
95
- # scope. You can upload attachments up to 200 MB. Certain file types aren't
96
- # supported. For details, see [File types blocked by Google Chat](https://
94
+ # auth/users). You can upload attachments up to 200 MB. Certain file types aren'
95
+ # t supported. For details, see [File types blocked by Google Chat](https://
97
96
  # support.google.com/chat/answer/7651457?&co=GENIE.Platform%3DDesktop#File%
98
97
  # 20types%20blocked%20in%20Google%20Chat).
99
98
  # @param [String] parent
@@ -144,8 +143,7 @@ module Google
144
143
  # spaces/create). If you receive the error message `ALREADY_EXISTS` when
145
144
  # creating a space, try a different `displayName`. An existing space within the
146
145
  # Google Workspace organization might already use this display name. Requires [
147
- # user authentication](https://developers.google.com/chat/api/guides/auth/users)
148
- # and the `chat.spaces.create` or `chat.spaces` scope.
146
+ # user authentication](https://developers.google.com/chat/api/guides/auth/users).
149
147
  # @param [Google::Apis::ChatV1::Space] space_object
150
148
  # @param [String] request_id
151
149
  # Optional. A unique identifier for this request. A random UUID is recommended.
@@ -186,7 +184,7 @@ module Google
186
184
  # in the space—are also deleted. For an example, see [Delete a space](https://
187
185
  # developers.google.com/chat/api/guides/v1/spaces/delete). Requires [user
188
186
  # authentication](https://developers.google.com/chat/api/guides/auth/users) from
189
- # a user who has permission to delete the space, and the `chat.delete` scope.
187
+ # a user who has permission to delete the space.
190
188
  # @param [String] name
191
189
  # Required. Resource name of the space to delete. Format: `spaces/`space``
192
190
  # @param [String] fields
@@ -271,8 +269,7 @@ module Google
271
269
  # account authentication](https://developers.google.com/chat/api/guides/auth/
272
270
  # service-accounts) and [user authentication](https://developers.google.com/chat/
273
271
  # api/guides/auth/users). [User authentication](https://developers.google.com/
274
- # chat/api/guides/auth/users) requires the `chat.spaces` or `chat.spaces.
275
- # readonly` authorization scope.
272
+ # chat/api/guides/auth/users).
276
273
  # @param [String] name
277
274
  # Required. Resource name of the space, in the form "spaces/*". Format: `spaces/`
278
275
  # space``
@@ -309,8 +306,7 @@ module Google
309
306
  # authentication](https://developers.google.com/chat/api/guides/auth). Fully
310
307
  # supports [service account authentication](https://developers.google.com/chat/
311
308
  # api/guides/auth/service-accounts) and [user authentication](https://developers.
312
- # google.com/chat/api/guides/auth/users) requires the `chat.spaces` or `chat.
313
- # spaces.readonly` authorization scope. Lists spaces visible to the caller or
309
+ # google.com/chat/api/guides/auth/users). Lists spaces visible to the caller or
314
310
  # authenticated user. Group chats and DMs aren't listed until the first message
315
311
  # is sent.
316
312
  # @param [String] filter
@@ -371,8 +367,7 @@ module Google
371
367
  # displayName` field and receive the error message `ALREADY_EXISTS`, try a
372
368
  # different display name.. An existing space within the Google Workspace
373
369
  # organization might already use this display name. Requires [user
374
- # authentication](https://developers.google.com/chat/api/guides/auth/users) and
375
- # the `chat.spaces` scope.
370
+ # authentication](https://developers.google.com/chat/api/guides/auth/users).
376
371
  # @param [String] name
377
372
  # Resource name of the space. Format: `spaces/`space``
378
373
  # @param [Google::Apis::ChatV1::Space] space_object
@@ -453,8 +448,7 @@ module Google
453
448
  # ALREADY_EXISTS` when setting up a space, try a different `displayName`. An
454
449
  # existing space within the Google Workspace organization might already use this
455
450
  # display name. Requires [user authentication](https://developers.google.com/
456
- # chat/api/guides/auth/users) and the `chat.spaces.create` or `chat.spaces`
457
- # scope.
451
+ # chat/api/guides/auth/users).
458
452
  # @param [Google::Apis::ChatV1::SetUpSpaceRequest] set_up_space_request_object
459
453
  # @param [String] fields
460
454
  # Selector specifying which fields to include in a partial response.
@@ -491,18 +485,16 @@ module Google
491
485
  # policy turned off, then they're invited, and must accept the space invitation
492
486
  # before joining. Otherwise, creating a membership adds the member directly to
493
487
  # the specified space. Requires [user authentication](https://developers.google.
494
- # com/chat/api/guides/auth/users) and the `chat.memberships` (for human
495
- # membership) or `chat.memberships.app` (for app membership) scope. To specify
496
- # the member to add, set the `membership.member.name` in the `
497
- # CreateMembershipRequest`: - To add the calling app to a space or a direct
498
- # message between two human users, use `users/app`. Unable to add other apps to
499
- # the space. - To add a human user, use `users/`user``, where ``user`` can be
500
- # the email address for the user. For users in the same Workspace organization ``
501
- # user`` can also be the ``person_id`` for the person from the People API, or
502
- # the `id` for the user in the Directory API. For example, if the People API
503
- # Person `resourceName` for `user@example.com` is `people/123456789`, you can
504
- # add the user to the space by setting the `membership.member.name` to `users/
505
- # user@example.com` or `users/123456789`.
488
+ # com/chat/api/guides/auth/users). To specify the member to add, set the `
489
+ # membership.member.name` in the `CreateMembershipRequest`: - To add the calling
490
+ # app to a space or a direct message between two human users, use `users/app`.
491
+ # Unable to add other apps to the space. - To add a human user, use `users/`user`
492
+ # `, where ``user`` can be the email address for the user. For users in the same
493
+ # Workspace organization ``user`` can also be the ``person_id`` for the person
494
+ # from the People API, or the `id` for the user in the Directory API. For
495
+ # example, if the People API Person `resourceName` for `user@example.com` is `
496
+ # people/123456789`, you can add the user to the space by setting the `
497
+ # membership.member.name` to `users/user@example.com` or `users/123456789`.
506
498
  # @param [String] parent
507
499
  # Required. The resource name of the space for which to create the membership.
508
500
  # Format: spaces/`space`
@@ -538,8 +530,7 @@ module Google
538
530
 
539
531
  # Deletes a membership. For an example, see [Delete a membership](https://
540
532
  # developers.google.com/chat/api/guides/v1/members/delete). Requires [user
541
- # authentication](https://developers.google.com/chat/api/guides/auth/users) and
542
- # the `chat.memberships` or `chat.memberships.app` authorization scope.
533
+ # authentication](https://developers.google.com/chat/api/guides/auth/users).
543
534
  # @param [String] name
544
535
  # Required. Resource name of the membership to delete. Chat apps can delete
545
536
  # human users' or their own memberships. Chat apps can't delete other apps'
@@ -583,8 +574,7 @@ module Google
583
574
  # supports [service account authentication](https://developers.google.com/chat/
584
575
  # api/guides/auth/service-accounts) and [user authentication](https://developers.
585
576
  # google.com/chat/api/guides/auth/users). [User authentication](https://
586
- # developers.google.com/chat/api/guides/auth/users) requires the `chat.
587
- # memberships` or `chat.memberships.readonly` authorization scope.
577
+ # developers.google.com/chat/api/guides/auth/users).
588
578
  # @param [String] name
589
579
  # Required. Resource name of the membership to retrieve. To get the app's own
590
580
  # membership, you can optionally use `spaces/`space`/members/app`. Format: `
@@ -631,8 +621,7 @@ module Google
631
621
  # Fully supports [service account authentication](https://developers.google.com/
632
622
  # chat/api/guides/auth/service-accounts) and [user authentication](https://
633
623
  # developers.google.com/chat/api/guides/auth/users). [User authentication](https:
634
- # //developers.google.com/chat/api/guides/auth/users) requires the `chat.
635
- # memberships` or `chat.memberships.readonly` authorization scope.
624
+ # //developers.google.com/chat/api/guides/auth/users).
636
625
  # @param [String] parent
637
626
  # Required. The resource name of the space for which to fetch a membership list.
638
627
  # Format: spaces/`space`
@@ -698,19 +687,13 @@ module Google
698
687
  execute_or_queue_command(command, &block)
699
688
  end
700
689
 
701
- # Creates a message. For an example, see [Create a message](https://developers.
702
- # google.com/chat/api/guides/crudl/messages#create_a_message). Requires [
703
- # authentication](https://developers.google.com/chat/api/guides/auth). Creating
704
- # a text message supports both [user authentication](https://developers.google.
705
- # com/chat/api/guides/auth/users) and [app authentication] (https://developers.
706
- # google.com/chat/api/guides/auth/service-accounts). [User authentication](https:
707
- # //developers.google.com/chat/api/guides/auth/users) requires the `chat.
708
- # messages` or `chat.messages.create` authorization scope. Creating a card
709
- # message only supports and requires [app authentication] (https://developers.
710
- # google.com/chat/api/guides/auth/service-accounts). Because Chat provides
711
- # authentication for [webhooks](https://developers.google.com/chat/how-tos/
712
- # webhooks) as part of the URL that's generated when a webhook is registered,
713
- # webhooks can create messages without a service account or user authentication.
690
+ # Creates a message in a Google Chat space. For an example, see [Create a
691
+ # message](https://developers.google.com/chat/api/guides/v1/messages/create).
692
+ # Calling this method requires [authentication](https://developers.google.com/
693
+ # chat/api/guides/auth) and supports the following authentication types: - For
694
+ # text messages, user authentication or app authentication are supported. - For
695
+ # card messages, only app authentication is supported. (Only Chat apps can
696
+ # create card messages.)
714
697
  # @param [String] parent
715
698
  # Required. The resource name of the space in which to create a message. Format:
716
699
  # `spaces/`space``
@@ -779,9 +762,8 @@ module Google
779
762
  # account authentication](https://developers.google.com/chat/api/guides/auth/
780
763
  # service-accounts) and [user authentication](https://developers.google.com/chat/
781
764
  # api/guides/auth/users). [User authentication](https://developers.google.com/
782
- # chat/api/guides/auth/users) requires the `chat.messages` authorization scope.
783
- # Requests authenticated with service accounts can only delete messages created
784
- # by the calling Chat app.
765
+ # chat/api/guides/auth/users). Requests authenticated with service accounts can
766
+ # only delete messages created by the calling Chat app.
785
767
  # @param [String] name
786
768
  # Required. Resource name of the message that you want to delete, in the form `
787
769
  # spaces/*/messages/*` Example: `spaces/AAAAAAAAAAA/messages/BBBBBBBBBBB.
@@ -826,9 +808,8 @@ module Google
826
808
  # supports [service account authentication](https://developers.google.com/chat/
827
809
  # api/guides/auth/service-accounts) and [user authentication](https://developers.
828
810
  # google.com/chat/api/guides/auth/users). [User authentication](https://
829
- # developers.google.com/chat/api/guides/auth/users) requires the `chat.messages`
830
- # or `chat.messages.readonly` authorization scope. Note: Might return a message
831
- # from a blocked member or space.
811
+ # developers.google.com/chat/api/guides/auth/users). Note: Might return a
812
+ # message from a blocked member or space.
832
813
  # @param [String] name
833
814
  # Required. Resource name of the message to retrieve. Format: `spaces/`space`/
834
815
  # messages/`message`` If the message begins with `client-`, then it has a custom
@@ -866,8 +847,7 @@ module Google
866
847
  # Lists messages in a space that the caller is a member of, including messages
867
848
  # from blocked members and spaces. For an example, see [List messages](/chat/api/
868
849
  # guides/v1/messages/list). Requires [user authentication](https://developers.
869
- # google.com/chat/api/guides/auth/users) and the `chat.messages` or `chat.
870
- # messages.readonly` authorization scope.
850
+ # google.com/chat/api/guides/auth/users).
871
851
  # @param [String] parent
872
852
  # Required. The resource name of the space to list messages from. Format: `
873
853
  # spaces/`space``
@@ -948,9 +928,9 @@ module Google
948
928
  # api/guides/auth). Fully supports [service account authentication](https://
949
929
  # developers.google.com/chat/api/guides/auth/service-accounts) and [user
950
930
  # authentication](https://developers.google.com/chat/api/guides/auth/users). [
951
- # User authentication](https://developers.google.com/chat/api/guides/auth/users)
952
- # requires the `chat.messages` authorization scope. Requests authenticated with
953
- # service accounts can only update messages created by the calling Chat app.
931
+ # User authentication](https://developers.google.com/chat/api/guides/auth/users).
932
+ # Requests authenticated with service accounts can only update messages created
933
+ # by the calling Chat app.
954
934
  # @param [String] name
955
935
  # Resource name in the form `spaces/*/messages/*`. Example: `spaces/AAAAAAAAAAA/
956
936
  # messages/BBBBBBBBBBB.BBBBBBBBBBB`
@@ -1005,9 +985,9 @@ module Google
1005
985
  # api/guides/auth). Fully supports [service account authentication](https://
1006
986
  # developers.google.com/chat/api/guides/auth/service-accounts) and [user
1007
987
  # authentication](https://developers.google.com/chat/api/guides/auth/users). [
1008
- # User authentication](https://developers.google.com/chat/api/guides/auth/users)
1009
- # requires the `chat.messages` authorization scope. Requests authenticated with
1010
- # service accounts can only update messages created by the calling Chat app.
988
+ # User authentication](https://developers.google.com/chat/api/guides/auth/users).
989
+ # Requests authenticated with service accounts can only update messages created
990
+ # by the calling Chat app.
1011
991
  # @param [String] name
1012
992
  # Resource name in the form `spaces/*/messages/*`. Example: `spaces/AAAAAAAAAAA/
1013
993
  # messages/BBBBBBBBBBB.BBBBBBBBBBB`
@@ -1093,8 +1073,7 @@ module Google
1093
1073
  # Creates a reaction and adds it to a message. For an example, see [Create a
1094
1074
  # reaction](https://developers.google.com/chat/api/guides/v1/reactions/create).
1095
1075
  # Requires [user authentication](https://developers.google.com/chat/api/guides/
1096
- # auth/users) and the `chat.messages`, `chat.messages.reactions`, or `chat.
1097
- # messages.reactions.create` scope. Only unicode emoji are supported.
1076
+ # auth/users). Only unicode emoji are supported.
1098
1077
  # @param [String] parent
1099
1078
  # Required. The message where the reaction is created. Format: `spaces/`space`/
1100
1079
  # messages/`message``
@@ -1130,8 +1109,7 @@ module Google
1130
1109
 
1131
1110
  # Deletes a reaction to a message. For an example, see [Delete a reaction](https:
1132
1111
  # //developers.google.com/chat/api/guides/v1/reactions/delete). Requires [user
1133
- # authentication](https://developers.google.com/chat/api/guides/auth/users) and
1134
- # the `chat.messages` or `chat.messages.reactions` scope.
1112
+ # authentication](https://developers.google.com/chat/api/guides/auth/users).
1135
1113
  # @param [String] name
1136
1114
  # Required. Name of the reaction to delete. Format: `spaces/`space`/messages/`
1137
1115
  # message`/reactions/`reaction``
@@ -1164,9 +1142,7 @@ module Google
1164
1142
 
1165
1143
  # Lists reactions to a message. For an example, see [List reactions](https://
1166
1144
  # developers.google.com/chat/api/guides/v1/reactions/list). Requires [user
1167
- # authentication](https://developers.google.com/chat/api/guides/auth/users) and `
1168
- # chat.messages`, `chat.messages.readonly`, `chat.messages.reactions`, or `chat.
1169
- # messages.reactions.readonly` scope.
1145
+ # authentication](https://developers.google.com/chat/api/guides/auth/users).
1170
1146
  # @param [String] parent
1171
1147
  # Required. The message users reacted to. Format: `spaces/`space`/messages/`
1172
1148
  # message``
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: google-apis-chat_v1
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.68.0
4
+ version: 0.70.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - Google LLC
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2023-08-13 00:00:00.000000000 Z
11
+ date: 2023-09-03 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: google-apis-core
@@ -58,7 +58,7 @@ licenses:
58
58
  metadata:
59
59
  bug_tracker_uri: https://github.com/googleapis/google-api-ruby-client/issues
60
60
  changelog_uri: https://github.com/googleapis/google-api-ruby-client/tree/main/generated/google-apis-chat_v1/CHANGELOG.md
61
- documentation_uri: https://googleapis.dev/ruby/google-apis-chat_v1/v0.68.0
61
+ documentation_uri: https://googleapis.dev/ruby/google-apis-chat_v1/v0.70.0
62
62
  source_code_uri: https://github.com/googleapis/google-api-ruby-client/tree/main/generated/google-apis-chat_v1
63
63
  post_install_message:
64
64
  rdoc_options: []
@@ -75,7 +75,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
75
75
  - !ruby/object:Gem::Version
76
76
  version: '0'
77
77
  requirements: []
78
- rubygems_version: 3.4.2
78
+ rubygems_version: 3.4.19
79
79
  signing_key:
80
80
  specification_version: 4
81
81
  summary: Simple REST client for Google Chat API V1