@googleapis/verifiedaccess 0.3.2 → 0.3.3

package/CHANGELOG.md

@@ -1,5 +1,12 @@
 # Changelog
 
+## [0.3.3](https://github.com/googleapis/google-api-nodejs-client/compare/verifiedaccess-v0.3.2...verifiedaccess-v0.3.3) (2022-07-04)
+
+
+### Bug Fixes
+
+* **verifiedaccess:** update the API ([b61d46f](https://github.com/googleapis/google-api-nodejs-client/commit/b61d46f9facc2c4082430786c9455c108fc077c2))
+
 ## [0.3.2](https://github.com/googleapis/google-api-nodejs-client/compare/verifiedaccess-v0.3.1...verifiedaccess-v0.3.2) (2022-06-21)
 
 

package/build/v1.d.ts

@@ -85,7 +85,7 @@ export declare namespace verifiedaccess_v1 {
         challenge?: Schema$SignedData;
     }
     /**
-     * A generic empty message that you can re-use to avoid defining duplicated empty messages in your APIs. A typical example is to use it as the request or the response type of an API method. For instance: service Foo { rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty); \} The JSON representation for `Empty` is empty JSON object `{\}`.
+     * A generic empty message that you can re-use to avoid defining duplicated empty messages in your APIs. A typical example is to use it as the request or the response type of an API method. For instance: service Foo { rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty); \}
      */
     export interface Schema$Empty {
     }

package/build/v2.d.ts

@@ -85,7 +85,7 @@ export declare namespace verifiedaccess_v2 {
         challenge?: string | null;
     }
     /**
-     * A generic empty message that you can re-use to avoid defining duplicated empty messages in your APIs. A typical example is to use it as the request or the response type of an API method. For instance: service Foo { rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty); \} The JSON representation for `Empty` is empty JSON object `{\}`.
+     * A generic empty message that you can re-use to avoid defining duplicated empty messages in your APIs. A typical example is to use it as the request or the response type of an API method. For instance: service Foo { rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty); \}
      */
     export interface Schema$Empty {
     }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@googleapis/verifiedaccess",
-  "version": "0.3.2",
+  "version": "0.3.3",
   "description": "verifiedaccess",
   "main": "build/index.js",
   "types": "build/index.d.ts",

package/v1.ts

@@ -138,7 +138,7 @@ export namespace verifiedaccess_v1 {
     challenge?: Schema$SignedData;
   }
   /**
-   * A generic empty message that you can re-use to avoid defining duplicated empty messages in your APIs. A typical example is to use it as the request or the response type of an API method. For instance: service Foo { rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty); \} The JSON representation for `Empty` is empty JSON object `{\}`.
+   * A generic empty message that you can re-use to avoid defining duplicated empty messages in your APIs. A typical example is to use it as the request or the response type of an API method. For instance: service Foo { rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty); \}
    */
   export interface Schema$Empty {}
   /**

package/v2.ts

@@ -138,7 +138,7 @@ export namespace verifiedaccess_v2 {
     challenge?: string | null;
   }
   /**
-   * A generic empty message that you can re-use to avoid defining duplicated empty messages in your APIs. A typical example is to use it as the request or the response type of an API method. For instance: service Foo { rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty); \} The JSON representation for `Empty` is empty JSON object `{\}`.
+   * A generic empty message that you can re-use to avoid defining duplicated empty messages in your APIs. A typical example is to use it as the request or the response type of an API method. For instance: service Foo { rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty); \}
    */
   export interface Schema$Empty {}
   /**