fix(workspaceevents): update the API

#### workspaceevents:v1

The following keys were changed:
- schemas.NotificationEndpoint.properties.pubsubTopic.description
- schemas.PayloadOptions.description
- schemas.Subscription.properties.payloadOptions.description

Author: yoshi-automation

discovery/workspaceevents-v1.json

@@ -486,7 +486,7 @@
       }
     }
   },
-  "revision": "20250629",
+  "revision": "20250708",
   "rootUrl": "https://workspaceevents.googleapis.com/",
   "schemas": {
     "ListSubscriptionsResponse": {
@@ -512,7 +512,7 @@
       "id": "NotificationEndpoint",
       "properties": {
         "pubsubTopic": {
-          "description": "Immutable. The Pub/Sub topic that receives events for the subscription. Format: `projects/{project}/topics/{topic}` You must create the topic in the same Google Cloud project where you create this subscription. Note: The Workspace Events API uses [ordering keys](https://cloud.google.com/pubsub/docs/ordering) for the benefit of sequential events. If the Cloud Pub/Sub topic has a [message storage policy](https://cloud.google.com/pubsub/docs/resource-location-restriction#exceptions) configured to exclude the nearest Google Cloud region, publishing events with ordering keys will fail. When the topic receives events, the events are encoded as Pub/Sub messages. For details, see the [Google Cloud Pub/Sub Protocol Binding for CloudEvents](https://github.com/googleapis/google-cloudevents/blob/main/docs/spec/pubsub.md).",
+          "description": "Immutable. The Pub/Sub topic that receives events for the subscription. Format: `projects/{project}/topics/{topic}` You must create the topic in the same Google Cloud project where you create this subscription. Note: The Google Workspace Events API uses [ordering keys](https://cloud.google.com/pubsub/docs/ordering) for the benefit of sequential events. If the Cloud Pub/Sub topic has a [message storage policy](https://cloud.google.com/pubsub/docs/resource-location-restriction#exceptions) configured to exclude the nearest Google Cloud region, publishing events with ordering keys will fail. When the topic receives events, the events are encoded as Pub/Sub messages. For details, see the [Google Cloud Pub/Sub Protocol Binding for CloudEvents](https://github.com/googleapis/google-cloudevents/blob/main/docs/spec/pubsub.md).",
           "type": "string"
         }
       },
@@ -554,7 +554,7 @@
       "type": "object"
     },
     "PayloadOptions": {
-      "description": "Options about what data to include in the event payload. Only supported for Google Chat events.",
+      "description": "Options about what data to include in the event payload. Only supported for Google Chat and Google Drive events.",
       "id": "PayloadOptions",
       "properties": {
         "fieldMask": {
@@ -643,7 +643,7 @@
         },
         "payloadOptions": {
           "$ref": "PayloadOptions",
-          "description": "Optional. Options about what data to include in the event payload. Only supported for Google Chat events."
+          "description": "Optional. Options about what data to include in the event payload. Only supported for Google Chat and Google Drive events."
         },
         "reconciling": {
           "description": "Output only. If `true`, the subscription is in the process of being updated.",

src/apis/workspaceevents/README.md

@@ -4,6 +4,15 @@
 
 > The Google Workspace Events API lets you subscribe to events and manage change notifications across Google Workspace applications.
 
+## Support status
+**Note**: Google provides multiple libraries for this service. This library is in
+maintenance mode, and will continue to be made available for users who have
+existing applications. If you're building a new application, or modernizing a
+legacy application, please use [@google-cloud/subscriptions](https://www.npmjs.com/package/@google-cloud/subscriptions) instead.
+The [@google-cloud/subscriptions](https://www.npmjs.com/package/@google-cloud/subscriptions) library is faster, easier to use, and better maintained.
+
+To learn more, see [Client Libraries Explained](https://cloud.google.com/apis/docs/client-libraries-explained).
+
 ## Installation
 
 ```sh

src/apis/workspaceevents/v1.ts

@@ -144,7 +144,7 @@ export namespace workspaceevents_v1 {
    */
   export interface Schema$NotificationEndpoint {
     /**
-     * Immutable. The Pub/Sub topic that receives events for the subscription. Format: `projects/{project\}/topics/{topic\}` You must create the topic in the same Google Cloud project where you create this subscription. Note: The Workspace Events API uses [ordering keys](https://cloud.google.com/pubsub/docs/ordering) for the benefit of sequential events. If the Cloud Pub/Sub topic has a [message storage policy](https://cloud.google.com/pubsub/docs/resource-location-restriction#exceptions) configured to exclude the nearest Google Cloud region, publishing events with ordering keys will fail. When the topic receives events, the events are encoded as Pub/Sub messages. For details, see the [Google Cloud Pub/Sub Protocol Binding for CloudEvents](https://github.com/googleapis/google-cloudevents/blob/main/docs/spec/pubsub.md).
+     * Immutable. The Pub/Sub topic that receives events for the subscription. Format: `projects/{project\}/topics/{topic\}` You must create the topic in the same Google Cloud project where you create this subscription. Note: The Google Workspace Events API uses [ordering keys](https://cloud.google.com/pubsub/docs/ordering) for the benefit of sequential events. If the Cloud Pub/Sub topic has a [message storage policy](https://cloud.google.com/pubsub/docs/resource-location-restriction#exceptions) configured to exclude the nearest Google Cloud region, publishing events with ordering keys will fail. When the topic receives events, the events are encoded as Pub/Sub messages. For details, see the [Google Cloud Pub/Sub Protocol Binding for CloudEvents](https://github.com/googleapis/google-cloudevents/blob/main/docs/spec/pubsub.md).
      */
     pubsubTopic?: string | null;
   }
@@ -174,7 +174,7 @@ export namespace workspaceevents_v1 {
     response?: {[key: string]: any} | null;
   }
   /**
-   * Options about what data to include in the event payload. Only supported for Google Chat events.
+   * Options about what data to include in the event payload. Only supported for Google Chat and Google Drive events.
    */
   export interface Schema$PayloadOptions {
     /**
@@ -240,7 +240,7 @@ export namespace workspaceevents_v1 {
      */
     notificationEndpoint?: Schema$NotificationEndpoint;
     /**
-     * Optional. Options about what data to include in the event payload. Only supported for Google Chat events.
+     * Optional. Options about what data to include in the event payload. Only supported for Google Chat and Google Drive events.
      */
     payloadOptions?: Schema$PayloadOptions;
     /**