vercel-api-js 0.22.0 → 0.22.1

package/.turbo/turbo-build.log

@@ -1,5 +1,5 @@
 
-> vercel-api-js@0.22.0 build /home/runner/work/openapi-clients/openapi-clients/packages/vercel-api-js
+> vercel-api-js@0.22.1 build /home/runner/work/openapi-clients/openapi-clients/packages/vercel-api-js
 > unbuild
 
 [info] Automatically detected entries: src/index [esm] [cjs] [dts]
@@ -10,5 +10,5 @@
 
 [log]   dist/index.mjs (total size: 33.2 kB, chunk size: 33.2 kB, exports: VercelApi)
 
-Σ Total dist size (byte size): 3.14 MB
+Σ Total dist size (byte size): 3.15 MB
 [log]

package/CHANGELOG.md

@@ -1,5 +1,14 @@
 # vercel-api-js
 
+## 0.22.1
+
+### Patch Changes
+
+- 5f0ac90: Update type for get custom deployment
+- 15c6623: [BREAKING] Change type order in filterProjectEnvs and related functions
+- e120dde: [BREAKING] Remove 'blobStores' field from resourceConfig in AuthUser schema
+- c808605: Add 'partial' field to UpdateResourceSecretsRequestBody and UpdateResourceSecretsByIdRequestBody
+
 ## 0.22.0
 
 ### Minor Changes

package/dist/index.d.cts

@@ -298,7 +298,7 @@ type AuthUser = {
     softBlock: {
         blockedAt: number;
         reason: 'BLOCKED_FOR_PLATFORM_ABUSE' | 'ENTERPRISE_TRIAL_ENDED' | 'FAIR_USE_LIMITS_EXCEEDED' | 'SUBSCRIPTION_CANCELED' | 'SUBSCRIPTION_EXPIRED' | 'UNPAID_INVOICE';
-        blockedDueToOverageType?: 'aiCredits' | 'analyticsUsage' | 'artifacts' | 'bandwidth' | 'blobStores' | 'blobTotalAdvancedRequests' | 'blobTotalAvgSizeInBytes' | 'blobTotalGetResponseObjectSizeInBytes' | 'blobTotalSimpleRequests' | 'buildMinute' | 'dataCacheRead' | 'dataCacheRevalidation' | 'dataCacheWrite' | 'edgeConfigRead' | 'edgeConfigWrite' | 'edgeFunctionExecutionUnits' | 'edgeMiddlewareInvocations' | 'edgeRequest' | 'edgeRequestAdditionalCpuDuration' | 'elasticConcurrencyBuildSlots' | 'fastDataTransfer' | 'fastOriginTransfer' | 'functionDuration' | 'functionInvocation' | 'imageOptimizationCacheRead' | 'imageOptimizationCacheWrite' | 'imageOptimizationTransformation' | 'logDrainsVolume' | 'monitoringMetric' | 'objectDataTransfer' | 'observabilityEvent' | 'postgresComputeTime' | 'postgresDataStorage' | 'postgresDataTransfer' | 'postgresDatabase' | 'postgresWrittenData' | 'serverlessFunctionExecution' | 'sourceImages' | 'storageRedisTotalBandwidthInBytes' | 'storageRedisTotalCommands' | 'storageRedisTotalDailyAvgStorageInBytes' | 'storageRedisTotalDatabases' | 'wafOwaspExcessBytes' | 'wafOwaspRequests' | 'wafRateLimitRequest' | 'webAnalyticsEvent';
+        blockedDueToOverageType?: 'aiCredits' | 'analyticsUsage' | 'artifacts' | 'bandwidth' | 'blobTotalAdvancedRequests' | 'blobTotalAvgSizeInBytes' | 'blobTotalGetResponseObjectSizeInBytes' | 'blobTotalSimpleRequests' | 'dataCacheRead' | 'dataCacheWrite' | 'edgeConfigRead' | 'edgeConfigWrite' | 'edgeFunctionExecutionUnits' | 'edgeMiddlewareInvocations' | 'edgeRequest' | 'edgeRequestAdditionalCpuDuration' | 'elasticConcurrencyBuildSlots' | 'fastDataTransfer' | 'fastOriginTransfer' | 'functionDuration' | 'functionInvocation' | 'imageOptimizationCacheRead' | 'imageOptimizationCacheWrite' | 'imageOptimizationTransformation' | 'logDrainsVolume' | 'monitoringMetric' | 'objectDataTransfer' | 'observabilityEvent' | 'postgresComputeTime' | 'postgresDataStorage' | 'postgresDataTransfer' | 'postgresDatabase' | 'postgresWrittenData' | 'serverlessFunctionExecution' | 'sourceImages' | 'storageRedisTotalBandwidthInBytes' | 'storageRedisTotalCommands' | 'storageRedisTotalDailyAvgStorageInBytes' | 'storageRedisTotalDatabases' | 'wafOwaspExcessBytes' | 'wafOwaspRequests' | 'wafRateLimitRequest' | 'webAnalyticsEvent';
     } | null;
     /**
      * An object containing billing infomation associated with the User account.
@@ -308,10 +308,6 @@ type AuthUser = {
      * An object containing infomation related to the amount of platform resources may be allocated to the User account.
      */
     resourceConfig: {
-        /**
-         * An object containing infomation related to the amount of platform resources may be allocated to the User account.
-         */
-        blobStores?: number;
         /**
          * An object containing infomation related to the amount of platform resources may be allocated to the User account.
          */
@@ -364,6 +360,10 @@ type AuthUser = {
          * An object containing infomation related to the amount of platform resources may be allocated to the User account.
          */
         postgresDatabases?: number;
+        /**
+         * An object containing infomation related to the amount of platform resources may be allocated to the User account.
+         */
+        blobStores?: number;
         /**
          * An object containing infomation related to the amount of platform resources may be allocated to the User account.
          */
@@ -2494,6 +2494,25 @@ type UpdateProjectDataCacheResponse = {
         functionZeroConfigFailover?: boolean;
         elasticConcurrencyEnabled?: boolean;
     };
+    rollingRelease?: {
+        /**
+         * The environment that the release targets, currently only supports production. Adding in case we want to configure with alias groups or custom environments.
+         */
+        target: string;
+        /**
+         * minutesToRelease is the total time to gradually shift percentages. This value overrides stages and instead creates a single smooth 0-100 stage. So once we have fetched the document with the start time, subtract from the current time, and divide by total minutesToRelease, to determine what percentage of traffic the new deployment should be serving. There is no approval required, and for the case of Vercel, it would just slowly shift traffic 0 to 100%.
+         */
+        minutesToRelease?: number;
+        /**
+         * An array of all the stages required during a deployment release. each stage requires an approval before advancing to the next stage.
+         */
+        stages?: {
+            /**
+             * The percentage of traffic to serve to the new deployment
+             */
+            targetPercentage: number;
+        }[] | null;
+    } | null;
     defaultResourceConfig: {
         fluid?: boolean;
         functionDefaultRegions: string[];
@@ -7377,7 +7396,7 @@ type SubmitBillingDataRequestBody = {
         /**
          * Partner's resource ID.
          */
-        resourceId: string;
+        resourceId?: string;
         /**
          * Metric name.
          */
@@ -7651,6 +7670,10 @@ type UpdateResourceSecretsRequestBody = {
         value: string;
         prefix?: string;
     }[];
+    /**
+     * If true, will only update the provided secrets
+     */
+    partial?: boolean;
 };
 type UpdateResourceSecretsVariables = {
     body: UpdateResourceSecretsRequestBody;
@@ -7671,6 +7694,10 @@ type UpdateResourceSecretsByIdRequestBody = {
         value: string;
         prefix?: string;
     }[];
+    /**
+     * If true, will only update the provided secrets
+     */
+    partial?: boolean;
 };
 type UpdateResourceSecretsByIdVariables = {
     body: UpdateResourceSecretsByIdRequestBody;
@@ -9491,6 +9518,25 @@ type GetProjectsResponse = {
             functionZeroConfigFailover?: boolean;
             elasticConcurrencyEnabled?: boolean;
         };
+        rollingRelease?: {
+            /**
+             * The environment that the release targets, currently only supports production. Adding in case we want to configure with alias groups or custom environments.
+             */
+            target: string;
+            /**
+             * minutesToRelease is the total time to gradually shift percentages. This value overrides stages and instead creates a single smooth 0-100 stage. So once we have fetched the document with the start time, subtract from the current time, and divide by total minutesToRelease, to determine what percentage of traffic the new deployment should be serving. There is no approval required, and for the case of Vercel, it would just slowly shift traffic 0 to 100%.
+             */
+            minutesToRelease?: number;
+            /**
+             * An array of all the stages required during a deployment release. each stage requires an approval before advancing to the next stage.
+             */
+            stages?: {
+                /**
+                 * The percentage of traffic to serve to the new deployment
+                 */
+                targetPercentage: number;
+            }[] | null;
+        } | null;
         defaultResourceConfig: {
             fluid?: boolean;
             functionDefaultRegions: string[];
@@ -10308,6 +10354,25 @@ type CreateProjectResponse = {
         functionZeroConfigFailover?: boolean;
         elasticConcurrencyEnabled?: boolean;
     };
+    rollingRelease?: {
+        /**
+         * The environment that the release targets, currently only supports production. Adding in case we want to configure with alias groups or custom environments.
+         */
+        target: string;
+        /**
+         * minutesToRelease is the total time to gradually shift percentages. This value overrides stages and instead creates a single smooth 0-100 stage. So once we have fetched the document with the start time, subtract from the current time, and divide by total minutesToRelease, to determine what percentage of traffic the new deployment should be serving. There is no approval required, and for the case of Vercel, it would just slowly shift traffic 0 to 100%.
+         */
+        minutesToRelease?: number;
+        /**
+         * An array of all the stages required during a deployment release. each stage requires an approval before advancing to the next stage.
+         */
+        stages?: {
+            /**
+             * The percentage of traffic to serve to the new deployment
+             */
+            targetPercentage: number;
+        }[] | null;
+    } | null;
     defaultResourceConfig: {
         fluid?: boolean;
         functionDefaultRegions: string[];
@@ -11257,6 +11322,25 @@ type GetProjectResponse = {
         functionZeroConfigFailover?: boolean;
         elasticConcurrencyEnabled?: boolean;
     };
+    rollingRelease?: {
+        /**
+         * The environment that the release targets, currently only supports production. Adding in case we want to configure with alias groups or custom environments.
+         */
+        target: string;
+        /**
+         * minutesToRelease is the total time to gradually shift percentages. This value overrides stages and instead creates a single smooth 0-100 stage. So once we have fetched the document with the start time, subtract from the current time, and divide by total minutesToRelease, to determine what percentage of traffic the new deployment should be serving. There is no approval required, and for the case of Vercel, it would just slowly shift traffic 0 to 100%.
+         */
+        minutesToRelease?: number;
+        /**
+         * An array of all the stages required during a deployment release. each stage requires an approval before advancing to the next stage.
+         */
+        stages?: {
+            /**
+             * The percentage of traffic to serve to the new deployment
+             */
+            targetPercentage: number;
+        }[] | null;
+    } | null;
     defaultResourceConfig: {
         fluid?: boolean;
         functionDefaultRegions: string[];
@@ -12081,6 +12165,25 @@ type UpdateProjectResponse = {
         functionZeroConfigFailover?: boolean;
         elasticConcurrencyEnabled?: boolean;
     };
+    rollingRelease?: {
+        /**
+         * The environment that the release targets, currently only supports production. Adding in case we want to configure with alias groups or custom environments.
+         */
+        target: string;
+        /**
+         * minutesToRelease is the total time to gradually shift percentages. This value overrides stages and instead creates a single smooth 0-100 stage. So once we have fetched the document with the start time, subtract from the current time, and divide by total minutesToRelease, to determine what percentage of traffic the new deployment should be serving. There is no approval required, and for the case of Vercel, it would just slowly shift traffic 0 to 100%.
+         */
+        minutesToRelease?: number;
+        /**
+         * An array of all the stages required during a deployment release. each stage requires an approval before advancing to the next stage.
+         */
+        stages?: {
+            /**
+             * The percentage of traffic to serve to the new deployment
+             */
+            targetPercentage: number;
+        }[] | null;
+    } | null;
     defaultResourceConfig: {
         fluid?: boolean;
         functionDefaultRegions: string[];

package/dist/index.d.mts

@@ -298,7 +298,7 @@ type AuthUser = {
     softBlock: {
         blockedAt: number;
         reason: 'BLOCKED_FOR_PLATFORM_ABUSE' | 'ENTERPRISE_TRIAL_ENDED' | 'FAIR_USE_LIMITS_EXCEEDED' | 'SUBSCRIPTION_CANCELED' | 'SUBSCRIPTION_EXPIRED' | 'UNPAID_INVOICE';
-        blockedDueToOverageType?: 'aiCredits' | 'analyticsUsage' | 'artifacts' | 'bandwidth' | 'blobStores' | 'blobTotalAdvancedRequests' | 'blobTotalAvgSizeInBytes' | 'blobTotalGetResponseObjectSizeInBytes' | 'blobTotalSimpleRequests' | 'buildMinute' | 'dataCacheRead' | 'dataCacheRevalidation' | 'dataCacheWrite' | 'edgeConfigRead' | 'edgeConfigWrite' | 'edgeFunctionExecutionUnits' | 'edgeMiddlewareInvocations' | 'edgeRequest' | 'edgeRequestAdditionalCpuDuration' | 'elasticConcurrencyBuildSlots' | 'fastDataTransfer' | 'fastOriginTransfer' | 'functionDuration' | 'functionInvocation' | 'imageOptimizationCacheRead' | 'imageOptimizationCacheWrite' | 'imageOptimizationTransformation' | 'logDrainsVolume' | 'monitoringMetric' | 'objectDataTransfer' | 'observabilityEvent' | 'postgresComputeTime' | 'postgresDataStorage' | 'postgresDataTransfer' | 'postgresDatabase' | 'postgresWrittenData' | 'serverlessFunctionExecution' | 'sourceImages' | 'storageRedisTotalBandwidthInBytes' | 'storageRedisTotalCommands' | 'storageRedisTotalDailyAvgStorageInBytes' | 'storageRedisTotalDatabases' | 'wafOwaspExcessBytes' | 'wafOwaspRequests' | 'wafRateLimitRequest' | 'webAnalyticsEvent';
+        blockedDueToOverageType?: 'aiCredits' | 'analyticsUsage' | 'artifacts' | 'bandwidth' | 'blobTotalAdvancedRequests' | 'blobTotalAvgSizeInBytes' | 'blobTotalGetResponseObjectSizeInBytes' | 'blobTotalSimpleRequests' | 'dataCacheRead' | 'dataCacheWrite' | 'edgeConfigRead' | 'edgeConfigWrite' | 'edgeFunctionExecutionUnits' | 'edgeMiddlewareInvocations' | 'edgeRequest' | 'edgeRequestAdditionalCpuDuration' | 'elasticConcurrencyBuildSlots' | 'fastDataTransfer' | 'fastOriginTransfer' | 'functionDuration' | 'functionInvocation' | 'imageOptimizationCacheRead' | 'imageOptimizationCacheWrite' | 'imageOptimizationTransformation' | 'logDrainsVolume' | 'monitoringMetric' | 'objectDataTransfer' | 'observabilityEvent' | 'postgresComputeTime' | 'postgresDataStorage' | 'postgresDataTransfer' | 'postgresDatabase' | 'postgresWrittenData' | 'serverlessFunctionExecution' | 'sourceImages' | 'storageRedisTotalBandwidthInBytes' | 'storageRedisTotalCommands' | 'storageRedisTotalDailyAvgStorageInBytes' | 'storageRedisTotalDatabases' | 'wafOwaspExcessBytes' | 'wafOwaspRequests' | 'wafRateLimitRequest' | 'webAnalyticsEvent';
     } | null;
     /**
      * An object containing billing infomation associated with the User account.
@@ -308,10 +308,6 @@ type AuthUser = {
      * An object containing infomation related to the amount of platform resources may be allocated to the User account.
      */
     resourceConfig: {
-        /**
-         * An object containing infomation related to the amount of platform resources may be allocated to the User account.
-         */
-        blobStores?: number;
         /**
          * An object containing infomation related to the amount of platform resources may be allocated to the User account.
          */
@@ -364,6 +360,10 @@ type AuthUser = {
          * An object containing infomation related to the amount of platform resources may be allocated to the User account.
          */
         postgresDatabases?: number;
+        /**
+         * An object containing infomation related to the amount of platform resources may be allocated to the User account.
+         */
+        blobStores?: number;
         /**
          * An object containing infomation related to the amount of platform resources may be allocated to the User account.
          */
@@ -2494,6 +2494,25 @@ type UpdateProjectDataCacheResponse = {
         functionZeroConfigFailover?: boolean;
         elasticConcurrencyEnabled?: boolean;
     };
+    rollingRelease?: {
+        /**
+         * The environment that the release targets, currently only supports production. Adding in case we want to configure with alias groups or custom environments.
+         */
+        target: string;
+        /**
+         * minutesToRelease is the total time to gradually shift percentages. This value overrides stages and instead creates a single smooth 0-100 stage. So once we have fetched the document with the start time, subtract from the current time, and divide by total minutesToRelease, to determine what percentage of traffic the new deployment should be serving. There is no approval required, and for the case of Vercel, it would just slowly shift traffic 0 to 100%.
+         */
+        minutesToRelease?: number;
+        /**
+         * An array of all the stages required during a deployment release. each stage requires an approval before advancing to the next stage.
+         */
+        stages?: {
+            /**
+             * The percentage of traffic to serve to the new deployment
+             */
+            targetPercentage: number;
+        }[] | null;
+    } | null;
     defaultResourceConfig: {
         fluid?: boolean;
         functionDefaultRegions: string[];
@@ -7377,7 +7396,7 @@ type SubmitBillingDataRequestBody = {
         /**
          * Partner's resource ID.
          */
-        resourceId: string;
+        resourceId?: string;
         /**
          * Metric name.
          */
@@ -7651,6 +7670,10 @@ type UpdateResourceSecretsRequestBody = {
         value: string;
         prefix?: string;
     }[];
+    /**
+     * If true, will only update the provided secrets
+     */
+    partial?: boolean;
 };
 type UpdateResourceSecretsVariables = {
     body: UpdateResourceSecretsRequestBody;
@@ -7671,6 +7694,10 @@ type UpdateResourceSecretsByIdRequestBody = {
         value: string;
         prefix?: string;
     }[];
+    /**
+     * If true, will only update the provided secrets
+     */
+    partial?: boolean;
 };
 type UpdateResourceSecretsByIdVariables = {
     body: UpdateResourceSecretsByIdRequestBody;
@@ -9491,6 +9518,25 @@ type GetProjectsResponse = {
             functionZeroConfigFailover?: boolean;
             elasticConcurrencyEnabled?: boolean;
         };
+        rollingRelease?: {
+            /**
+             * The environment that the release targets, currently only supports production. Adding in case we want to configure with alias groups or custom environments.
+             */
+            target: string;
+            /**
+             * minutesToRelease is the total time to gradually shift percentages. This value overrides stages and instead creates a single smooth 0-100 stage. So once we have fetched the document with the start time, subtract from the current time, and divide by total minutesToRelease, to determine what percentage of traffic the new deployment should be serving. There is no approval required, and for the case of Vercel, it would just slowly shift traffic 0 to 100%.
+             */
+            minutesToRelease?: number;
+            /**
+             * An array of all the stages required during a deployment release. each stage requires an approval before advancing to the next stage.
+             */
+            stages?: {
+                /**
+                 * The percentage of traffic to serve to the new deployment
+                 */
+                targetPercentage: number;
+            }[] | null;
+        } | null;
         defaultResourceConfig: {
             fluid?: boolean;
             functionDefaultRegions: string[];
@@ -10308,6 +10354,25 @@ type CreateProjectResponse = {
         functionZeroConfigFailover?: boolean;
         elasticConcurrencyEnabled?: boolean;
     };
+    rollingRelease?: {
+        /**
+         * The environment that the release targets, currently only supports production. Adding in case we want to configure with alias groups or custom environments.
+         */
+        target: string;
+        /**
+         * minutesToRelease is the total time to gradually shift percentages. This value overrides stages and instead creates a single smooth 0-100 stage. So once we have fetched the document with the start time, subtract from the current time, and divide by total minutesToRelease, to determine what percentage of traffic the new deployment should be serving. There is no approval required, and for the case of Vercel, it would just slowly shift traffic 0 to 100%.
+         */
+        minutesToRelease?: number;
+        /**
+         * An array of all the stages required during a deployment release. each stage requires an approval before advancing to the next stage.
+         */
+        stages?: {
+            /**
+             * The percentage of traffic to serve to the new deployment
+             */
+            targetPercentage: number;
+        }[] | null;
+    } | null;
     defaultResourceConfig: {
         fluid?: boolean;
         functionDefaultRegions: string[];
@@ -11257,6 +11322,25 @@ type GetProjectResponse = {
         functionZeroConfigFailover?: boolean;
         elasticConcurrencyEnabled?: boolean;
     };
+    rollingRelease?: {
+        /**
+         * The environment that the release targets, currently only supports production. Adding in case we want to configure with alias groups or custom environments.
+         */
+        target: string;
+        /**
+         * minutesToRelease is the total time to gradually shift percentages. This value overrides stages and instead creates a single smooth 0-100 stage. So once we have fetched the document with the start time, subtract from the current time, and divide by total minutesToRelease, to determine what percentage of traffic the new deployment should be serving. There is no approval required, and for the case of Vercel, it would just slowly shift traffic 0 to 100%.
+         */
+        minutesToRelease?: number;
+        /**
+         * An array of all the stages required during a deployment release. each stage requires an approval before advancing to the next stage.
+         */
+        stages?: {
+            /**
+             * The percentage of traffic to serve to the new deployment
+             */
+            targetPercentage: number;
+        }[] | null;
+    } | null;
     defaultResourceConfig: {
         fluid?: boolean;
         functionDefaultRegions: string[];
@@ -12081,6 +12165,25 @@ type UpdateProjectResponse = {
         functionZeroConfigFailover?: boolean;
         elasticConcurrencyEnabled?: boolean;
     };
+    rollingRelease?: {
+        /**
+         * The environment that the release targets, currently only supports production. Adding in case we want to configure with alias groups or custom environments.
+         */
+        target: string;
+        /**
+         * minutesToRelease is the total time to gradually shift percentages. This value overrides stages and instead creates a single smooth 0-100 stage. So once we have fetched the document with the start time, subtract from the current time, and divide by total minutesToRelease, to determine what percentage of traffic the new deployment should be serving. There is no approval required, and for the case of Vercel, it would just slowly shift traffic 0 to 100%.
+         */
+        minutesToRelease?: number;
+        /**
+         * An array of all the stages required during a deployment release. each stage requires an approval before advancing to the next stage.
+         */
+        stages?: {
+            /**
+             * The percentage of traffic to serve to the new deployment
+             */
+            targetPercentage: number;
+        }[] | null;
+    } | null;
     defaultResourceConfig: {
         fluid?: boolean;
         functionDefaultRegions: string[];

package/dist/index.d.ts

@@ -298,7 +298,7 @@ type AuthUser = {
     softBlock: {
         blockedAt: number;
         reason: 'BLOCKED_FOR_PLATFORM_ABUSE' | 'ENTERPRISE_TRIAL_ENDED' | 'FAIR_USE_LIMITS_EXCEEDED' | 'SUBSCRIPTION_CANCELED' | 'SUBSCRIPTION_EXPIRED' | 'UNPAID_INVOICE';
-        blockedDueToOverageType?: 'aiCredits' | 'analyticsUsage' | 'artifacts' | 'bandwidth' | 'blobStores' | 'blobTotalAdvancedRequests' | 'blobTotalAvgSizeInBytes' | 'blobTotalGetResponseObjectSizeInBytes' | 'blobTotalSimpleRequests' | 'buildMinute' | 'dataCacheRead' | 'dataCacheRevalidation' | 'dataCacheWrite' | 'edgeConfigRead' | 'edgeConfigWrite' | 'edgeFunctionExecutionUnits' | 'edgeMiddlewareInvocations' | 'edgeRequest' | 'edgeRequestAdditionalCpuDuration' | 'elasticConcurrencyBuildSlots' | 'fastDataTransfer' | 'fastOriginTransfer' | 'functionDuration' | 'functionInvocation' | 'imageOptimizationCacheRead' | 'imageOptimizationCacheWrite' | 'imageOptimizationTransformation' | 'logDrainsVolume' | 'monitoringMetric' | 'objectDataTransfer' | 'observabilityEvent' | 'postgresComputeTime' | 'postgresDataStorage' | 'postgresDataTransfer' | 'postgresDatabase' | 'postgresWrittenData' | 'serverlessFunctionExecution' | 'sourceImages' | 'storageRedisTotalBandwidthInBytes' | 'storageRedisTotalCommands' | 'storageRedisTotalDailyAvgStorageInBytes' | 'storageRedisTotalDatabases' | 'wafOwaspExcessBytes' | 'wafOwaspRequests' | 'wafRateLimitRequest' | 'webAnalyticsEvent';
+        blockedDueToOverageType?: 'aiCredits' | 'analyticsUsage' | 'artifacts' | 'bandwidth' | 'blobTotalAdvancedRequests' | 'blobTotalAvgSizeInBytes' | 'blobTotalGetResponseObjectSizeInBytes' | 'blobTotalSimpleRequests' | 'dataCacheRead' | 'dataCacheWrite' | 'edgeConfigRead' | 'edgeConfigWrite' | 'edgeFunctionExecutionUnits' | 'edgeMiddlewareInvocations' | 'edgeRequest' | 'edgeRequestAdditionalCpuDuration' | 'elasticConcurrencyBuildSlots' | 'fastDataTransfer' | 'fastOriginTransfer' | 'functionDuration' | 'functionInvocation' | 'imageOptimizationCacheRead' | 'imageOptimizationCacheWrite' | 'imageOptimizationTransformation' | 'logDrainsVolume' | 'monitoringMetric' | 'objectDataTransfer' | 'observabilityEvent' | 'postgresComputeTime' | 'postgresDataStorage' | 'postgresDataTransfer' | 'postgresDatabase' | 'postgresWrittenData' | 'serverlessFunctionExecution' | 'sourceImages' | 'storageRedisTotalBandwidthInBytes' | 'storageRedisTotalCommands' | 'storageRedisTotalDailyAvgStorageInBytes' | 'storageRedisTotalDatabases' | 'wafOwaspExcessBytes' | 'wafOwaspRequests' | 'wafRateLimitRequest' | 'webAnalyticsEvent';
     } | null;
     /**
      * An object containing billing infomation associated with the User account.
@@ -308,10 +308,6 @@ type AuthUser = {
      * An object containing infomation related to the amount of platform resources may be allocated to the User account.
      */
     resourceConfig: {
-        /**
-         * An object containing infomation related to the amount of platform resources may be allocated to the User account.
-         */
-        blobStores?: number;
         /**
          * An object containing infomation related to the amount of platform resources may be allocated to the User account.
          */
@@ -364,6 +360,10 @@ type AuthUser = {
          * An object containing infomation related to the amount of platform resources may be allocated to the User account.
          */
         postgresDatabases?: number;
+        /**
+         * An object containing infomation related to the amount of platform resources may be allocated to the User account.
+         */
+        blobStores?: number;
         /**
          * An object containing infomation related to the amount of platform resources may be allocated to the User account.
          */
@@ -2494,6 +2494,25 @@ type UpdateProjectDataCacheResponse = {
         functionZeroConfigFailover?: boolean;
         elasticConcurrencyEnabled?: boolean;
     };
+    rollingRelease?: {
+        /**
+         * The environment that the release targets, currently only supports production. Adding in case we want to configure with alias groups or custom environments.
+         */
+        target: string;
+        /**
+         * minutesToRelease is the total time to gradually shift percentages. This value overrides stages and instead creates a single smooth 0-100 stage. So once we have fetched the document with the start time, subtract from the current time, and divide by total minutesToRelease, to determine what percentage of traffic the new deployment should be serving. There is no approval required, and for the case of Vercel, it would just slowly shift traffic 0 to 100%.
+         */
+        minutesToRelease?: number;
+        /**
+         * An array of all the stages required during a deployment release. each stage requires an approval before advancing to the next stage.
+         */
+        stages?: {
+            /**
+             * The percentage of traffic to serve to the new deployment
+             */
+            targetPercentage: number;
+        }[] | null;
+    } | null;
     defaultResourceConfig: {
         fluid?: boolean;
         functionDefaultRegions: string[];
@@ -7377,7 +7396,7 @@ type SubmitBillingDataRequestBody = {
         /**
          * Partner's resource ID.
          */
-        resourceId: string;
+        resourceId?: string;
         /**
          * Metric name.
          */
@@ -7651,6 +7670,10 @@ type UpdateResourceSecretsRequestBody = {
         value: string;
         prefix?: string;
     }[];
+    /**
+     * If true, will only update the provided secrets
+     */
+    partial?: boolean;
 };
 type UpdateResourceSecretsVariables = {
     body: UpdateResourceSecretsRequestBody;
@@ -7671,6 +7694,10 @@ type UpdateResourceSecretsByIdRequestBody = {
         value: string;
         prefix?: string;
     }[];
+    /**
+     * If true, will only update the provided secrets
+     */
+    partial?: boolean;
 };
 type UpdateResourceSecretsByIdVariables = {
     body: UpdateResourceSecretsByIdRequestBody;
@@ -9491,6 +9518,25 @@ type GetProjectsResponse = {
             functionZeroConfigFailover?: boolean;
             elasticConcurrencyEnabled?: boolean;
         };
+        rollingRelease?: {
+            /**
+             * The environment that the release targets, currently only supports production. Adding in case we want to configure with alias groups or custom environments.
+             */
+            target: string;
+            /**
+             * minutesToRelease is the total time to gradually shift percentages. This value overrides stages and instead creates a single smooth 0-100 stage. So once we have fetched the document with the start time, subtract from the current time, and divide by total minutesToRelease, to determine what percentage of traffic the new deployment should be serving. There is no approval required, and for the case of Vercel, it would just slowly shift traffic 0 to 100%.
+             */
+            minutesToRelease?: number;
+            /**
+             * An array of all the stages required during a deployment release. each stage requires an approval before advancing to the next stage.
+             */
+            stages?: {
+                /**
+                 * The percentage of traffic to serve to the new deployment
+                 */
+                targetPercentage: number;
+            }[] | null;
+        } | null;
         defaultResourceConfig: {
             fluid?: boolean;
             functionDefaultRegions: string[];
@@ -10308,6 +10354,25 @@ type CreateProjectResponse = {
         functionZeroConfigFailover?: boolean;
         elasticConcurrencyEnabled?: boolean;
     };
+    rollingRelease?: {
+        /**
+         * The environment that the release targets, currently only supports production. Adding in case we want to configure with alias groups or custom environments.
+         */
+        target: string;
+        /**
+         * minutesToRelease is the total time to gradually shift percentages. This value overrides stages and instead creates a single smooth 0-100 stage. So once we have fetched the document with the start time, subtract from the current time, and divide by total minutesToRelease, to determine what percentage of traffic the new deployment should be serving. There is no approval required, and for the case of Vercel, it would just slowly shift traffic 0 to 100%.
+         */
+        minutesToRelease?: number;
+        /**
+         * An array of all the stages required during a deployment release. each stage requires an approval before advancing to the next stage.
+         */
+        stages?: {
+            /**
+             * The percentage of traffic to serve to the new deployment
+             */
+            targetPercentage: number;
+        }[] | null;
+    } | null;
     defaultResourceConfig: {
         fluid?: boolean;
         functionDefaultRegions: string[];
@@ -11257,6 +11322,25 @@ type GetProjectResponse = {
         functionZeroConfigFailover?: boolean;
         elasticConcurrencyEnabled?: boolean;
     };
+    rollingRelease?: {
+        /**
+         * The environment that the release targets, currently only supports production. Adding in case we want to configure with alias groups or custom environments.
+         */
+        target: string;
+        /**
+         * minutesToRelease is the total time to gradually shift percentages. This value overrides stages and instead creates a single smooth 0-100 stage. So once we have fetched the document with the start time, subtract from the current time, and divide by total minutesToRelease, to determine what percentage of traffic the new deployment should be serving. There is no approval required, and for the case of Vercel, it would just slowly shift traffic 0 to 100%.
+         */
+        minutesToRelease?: number;
+        /**
+         * An array of all the stages required during a deployment release. each stage requires an approval before advancing to the next stage.
+         */
+        stages?: {
+            /**
+             * The percentage of traffic to serve to the new deployment
+             */
+            targetPercentage: number;
+        }[] | null;
+    } | null;
     defaultResourceConfig: {
         fluid?: boolean;
         functionDefaultRegions: string[];
@@ -12081,6 +12165,25 @@ type UpdateProjectResponse = {
         functionZeroConfigFailover?: boolean;
         elasticConcurrencyEnabled?: boolean;
     };
+    rollingRelease?: {
+        /**
+         * The environment that the release targets, currently only supports production. Adding in case we want to configure with alias groups or custom environments.
+         */
+        target: string;
+        /**
+         * minutesToRelease is the total time to gradually shift percentages. This value overrides stages and instead creates a single smooth 0-100 stage. So once we have fetched the document with the start time, subtract from the current time, and divide by total minutesToRelease, to determine what percentage of traffic the new deployment should be serving. There is no approval required, and for the case of Vercel, it would just slowly shift traffic 0 to 100%.
+         */
+        minutesToRelease?: number;
+        /**
+         * An array of all the stages required during a deployment release. each stage requires an approval before advancing to the next stage.
+         */
+        stages?: {
+            /**
+             * The percentage of traffic to serve to the new deployment
+             */
+            targetPercentage: number;
+        }[] | null;
+    } | null;
     defaultResourceConfig: {
         fluid?: boolean;
         functionDefaultRegions: string[];

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "vercel-api-js",
-  "version": "0.22.0",
+  "version": "0.22.1",
   "description": "Vercel auto-generated type-safe API client",
   "author": "SferaDev",
   "license": "ISC",