@uipath/solution-tool 1.203.0-preview.212 → 1.204.0-preview.211

package/dist/prepare-solution-resources-wds3r8bq.js

@@ -1,22 +0,0 @@
-import {
-  prepareSolutionResources,
-  projectSubTypesFrom
-} from "./packager-tool-7znqtw3f.js";
-import"./packager-tool-znakt6yw.js";
-import"./packager-tool-k4mskzww.js";
-import"./packager-tool-jz2wbfjz.js";
-import"./packager-tool-bkwnetqn.js";
-import"./packager-tool-gdtpsdn7.js";
-import"./packager-tool-53w8skv5.js";
-import"./packager-tool-nzghfa48.js";
-import"./packager-tool-2syrt51a.js";
-import"./packager-tool-3jrq7smt.js";
-import"./packager-tool-0f0wt9vh.js";
-import"./packager-tool-dfrk01gn.js";
-import"./packager-tool-1de529jm.js";
-export {
-  prepareSolutionResources,
-  projectSubTypesFrom
-};
-
-//# debugId=9F446E87789120A364756E2164756E21

package/dist/services/personal-workspace-deploy.d.ts

@@ -1,49 +0,0 @@
-import type { SolutionAuthContext } from "@uipath/solution-sdk/auth";
-export interface FeedDeployResult {
-    deploymentName: string;
-    packageName: string;
-    packageVersion: string;
-    folderFQN: string;
-}
-export interface FeedDeployParams {
-    packageName: string;
-    packageVersion: string;
-    /** Caller-chosen deployment name (`deploy run --name`). */
-    deploymentName: string;
-    /** Name of the new Orchestrator folder created for the deployment (`--folder-name`). */
-    solutionRootFolderName: string;
-    /** Leave the deployment inactive instead of activating right after install. */
-    skipActivate?: boolean;
-}
-export interface FeedDeployTarget {
-    /** Folder key of the feed the package lives in — scopes the package lookup
-     *  and the deploy via the `X-UIPATH-FolderKey` header. */
-    feedFolderKey: string;
-    /** Folder key of the location the deployment installs into (the feed
-     *  folder itself or a validated descendant). The server creates the
-     *  solution root folder *under this key* — passing the feed key for a
-     *  descendant location silently installs in the feed root. */
-    locationFolderKey: string;
-    /** FQN of that same location — recorded as the deployment's path, so it
-     *  must agree with `locationFolderKey`. */
-    locationFQN: string;
-}
-/**
- * Deploy a feed-scoped solution package via the Automation Solutions
- * v2 auto-install endpoint.
- *
- * The tenant `deploy run` path (Pipelines `deploy-from-package`) resolves the
- * package from the tenant feed and cannot see a package published to a folder
- * or Personal Workspace feed. This path uses the feed-aware
- * `POST /api/v2/deployments/auto-install` endpoint instead (the same call
- * Studio Web makes for a deploy-only flow):
- *  - `target.feedFolderKey` scopes the package lookup and the deploy;
- *  - `target.locationFolderKey` / `target.locationFQN` say where the solution
- *    root folder is created (the feed folder or a descendant, already
- *    validated by the caller);
- *  - `deploymentName` / `solutionRootFolderName` are honored — unlike the
- *    older `POST /api/deployments/deploy`, which auto-named the deployment
- *    `AutoDeploy-<solution>`;
- *  - the server activates right after install unless `skipActivate` is set.
- */
-export declare function deployToFeed(auth: SolutionAuthContext, target: FeedDeployTarget, params: FeedDeployParams): Promise<FeedDeployResult>;