@vercel/sdk 1.11.1 → 1.11.2

package/esm/models/getdeploymentop.d.ts

@@ -1517,15 +1517,15 @@ export type GetDeploymentMicrofrontendsApplications = {
     deploymentHost?: string | undefined;
 };
 /**
- * The result of the microfrontends config upload during deployment creation. Only set for default app deployments. - `success` - The config was uploaded successfully. - `error` - The config upload failed. - `no_config` - No config was found to upload. - `undefined` - The config upload has not been attempted yet.
+ * The result of the microfrontends config upload during deployment creation / build. Only set for default app deployments. The config upload is attempted during deployment create, and then again during the build. If the config is not in the root directory, or the deployment is prebuilt, the config cannot be uploaded during deployment create. The upload during deployment build finds the config even if it's not in the root directory, as it has access to all files. Uploading the config during create is ideal, as then all child deployments are guaranteed to have access to the default app deployment config even if the default app has not yet started building. If the config is not uploaded, the child app will show as building until the config has been uploaded during the default app build. - `success` - The config was uploaded successfully, either when the deployment was created or during the build. - `waiting_on_build` - The config could not be uploaded during deployment create, will be attempted again during the build. - `no_config` - No config was found. Only set once the build has not found the config in any of the deployment's files. - `undefined` - Legacy deployments, or there was an error uploading the config during deployment create.
  */
 export declare const GetDeploymentMicrofrontendsMfeConfigUploadState: {
-    readonly Error: "error";
     readonly Success: "success";
+    readonly WaitingOnBuild: "waiting_on_build";
     readonly NoConfig: "no_config";
 };
 /**
- * The result of the microfrontends config upload during deployment creation. Only set for default app deployments. - `success` - The config was uploaded successfully. - `error` - The config upload failed. - `no_config` - No config was found to upload. - `undefined` - The config upload has not been attempted yet.
+ * The result of the microfrontends config upload during deployment creation / build. Only set for default app deployments. The config upload is attempted during deployment create, and then again during the build. If the config is not in the root directory, or the deployment is prebuilt, the config cannot be uploaded during deployment create. The upload during deployment build finds the config even if it's not in the root directory, as it has access to all files. Uploading the config during create is ideal, as then all child deployments are guaranteed to have access to the default app deployment config even if the default app has not yet started building. If the config is not uploaded, the child app will show as building until the config has been uploaded during the default app build. - `success` - The config was uploaded successfully, either when the deployment was created or during the build. - `waiting_on_build` - The config could not be uploaded during deployment create, will be attempted again during the build. - `no_config` - No config was found. Only set once the build has not found the config in any of the deployment's files. - `undefined` - Legacy deployments, or there was an error uploading the config during deployment create.
  */
 export type GetDeploymentMicrofrontendsMfeConfigUploadState = ClosedEnum<typeof GetDeploymentMicrofrontendsMfeConfigUploadState>;
 export type GetDeploymentMicrofrontends2 = {
@@ -1537,7 +1537,7 @@ export type GetDeploymentMicrofrontends2 = {
         [k: string]: GetDeploymentMicrofrontendsApplications;
     } | undefined;
     /**
-     * The result of the microfrontends config upload during deployment creation. Only set for default app deployments. - `success` - The config was uploaded successfully. - `error` - The config upload failed. - `no_config` - No config was found to upload. - `undefined` - The config upload has not been attempted yet.
+     * The result of the microfrontends config upload during deployment creation / build. Only set for default app deployments. The config upload is attempted during deployment create, and then again during the build. If the config is not in the root directory, or the deployment is prebuilt, the config cannot be uploaded during deployment create. The upload during deployment build finds the config even if it's not in the root directory, as it has access to all files. Uploading the config during create is ideal, as then all child deployments are guaranteed to have access to the default app deployment config even if the default app has not yet started building. If the config is not uploaded, the child app will show as building until the config has been uploaded during the default app build. - `success` - The config was uploaded successfully, either when the deployment was created or during the build. - `waiting_on_build` - The config could not be uploaded during deployment create, will be attempted again during the build. - `no_config` - No config was found. Only set once the build has not found the config in any of the deployment's files. - `undefined` - Legacy deployments, or there was an error uploading the config during deployment create.
      */
     mfeConfigUploadState?: GetDeploymentMicrofrontendsMfeConfigUploadState | undefined;
     /**
@@ -6578,14 +6578,14 @@ export declare const GetDeploymentMicrofrontendsMfeConfigUploadState$outboundSch
 export declare namespace GetDeploymentMicrofrontendsMfeConfigUploadState$ {
     /** @deprecated use `GetDeploymentMicrofrontendsMfeConfigUploadState$inboundSchema` instead. */
     const inboundSchema: z.ZodNativeEnum<{
-        readonly Error: "error";
         readonly Success: "success";
+        readonly WaitingOnBuild: "waiting_on_build";
         readonly NoConfig: "no_config";
     }>;
     /** @deprecated use `GetDeploymentMicrofrontendsMfeConfigUploadState$outboundSchema` instead. */
     const outboundSchema: z.ZodNativeEnum<{
-        readonly Error: "error";
         readonly Success: "success";
+        readonly WaitingOnBuild: "waiting_on_build";
         readonly NoConfig: "no_config";
     }>;
 }

package/esm/models/getdeploymentop.js

@@ -425,11 +425,11 @@ export const GetDeploymentGitRepoDeploymentsOwnerType = {
     User: "user",
 };
 /**
- * The result of the microfrontends config upload during deployment creation. Only set for default app deployments. - `success` - The config was uploaded successfully. - `error` - The config upload failed. - `no_config` - No config was found to upload. - `undefined` - The config upload has not been attempted yet.
+ * The result of the microfrontends config upload during deployment creation / build. Only set for default app deployments. The config upload is attempted during deployment create, and then again during the build. If the config is not in the root directory, or the deployment is prebuilt, the config cannot be uploaded during deployment create. The upload during deployment build finds the config even if it's not in the root directory, as it has access to all files. Uploading the config during create is ideal, as then all child deployments are guaranteed to have access to the default app deployment config even if the default app has not yet started building. If the config is not uploaded, the child app will show as building until the config has been uploaded during the default app build. - `success` - The config was uploaded successfully, either when the deployment was created or during the build. - `waiting_on_build` - The config could not be uploaded during deployment create, will be attempted again during the build. - `no_config` - No config was found. Only set once the build has not found the config in any of the deployment's files. - `undefined` - Legacy deployments, or there was an error uploading the config during deployment create.
  */
 export const GetDeploymentMicrofrontendsMfeConfigUploadState = {
-    Error: "error",
     Success: "success",
+    WaitingOnBuild: "waiting_on_build",
     NoConfig: "no_config",
 };
 export const ResponseBodyFunctionType = {