@maxim_mazurok/gapi.client.servicemanagement-v1 0.0.20250127 → 0.0.20250202

package/index.d.ts

@@ -9,7 +9,7 @@
 // This file was generated by https://github.com/Maxim-Mazurok/google-api-typings-generator. Please do not edit it manually.
 // In case of any problems please post issue to https://github.com/Maxim-Mazurok/google-api-typings-generator
 // Generated from: https://servicemanagement.googleapis.com/$discovery/rest?version=v1
-// Revision: 20250127
+// Revision: 20250202
 
 /// <reference types="gapi.client" />
 
@@ -338,6 +338,8 @@ declare namespace gapi.client {
       protobufPythonicTypesEnabled?: boolean;
       /** Enables generation of asynchronous REST clients if `rest` transport is enabled. By default, asynchronous REST clients will not be generated. This feature will be enabled by default 1 month after launching the feature in preview packages. */
       restAsyncIoEnabled?: boolean;
+      /** Disables generation of an unversioned Python package for this client library. This means that the module names will need to be versioned in import statements. For example `import google.cloud.library_v2` instead of `import google.cloud.library`. */
+      unversionedPackageDisabled?: boolean;
     }
     interface Expr {
       /** Optional. Description of the expression. This is a longer text which describes the expression, e.g. when hovered over it in a UI. */
@@ -676,7 +678,7 @@ declare namespace gapi.client {
       value?: {[P in string]: any};
     }
     interface Page {
-      /** The Markdown content of the page. You can use (== include {path} ==) to include content from a Markdown file. The content can be used to produce the documentation page such as HTML format page. */
+      /** The Markdown content of the page. You can use ```(== include {path} ==)``` to include content from a Markdown file. The content can be used to produce the documentation page such as HTML format page. */
       content?: string;
       /** The name of the page. It will be used as an identity of the page to generate URI of the page, text of the link to this page in navigation, etc. The full page name (start from the root page name to this page concatenated with `.`) can be used as reference to the page in your documentation. For example: pages: - name: Tutorial content: (== include tutorial.md ==) subpages: - name: Java content: (== include tutorial_java.md ==) You can reference `Java` page using Markdown reference link syntax: `Java`. */
       name?: string;
@@ -782,6 +784,8 @@ declare namespace gapi.client {
       common?: CommonLanguageSettings;
     }
     interface SelectiveGapicGeneration {
+      /** Setting this to true indicates to the client generators that methods that would be excluded from the generation should instead be generated in a way that indicates these methods should not be consumed by end users. How this is expressed is up to individual language implementations to decide. Some examples may be: added annotations, obfuscated identifiers, or other language idiomatic patterns. */
+      generateOmittedAsInternal?: boolean;
       /** An allowlist of the fully qualified names of RPCs that should be included on public client surfaces. */
       methods?: string[];
     }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@maxim_mazurok/gapi.client.servicemanagement-v1",
-  "version": "0.0.20250127",
+  "version": "0.0.20250202",
   "description": "TypeScript typings for Service Management API v1",
   "repository": {
     "type": "git",