@uipath/solution-tool 1.198.0 → 1.199.0-preview.105

package/dist/services/deploy-list-service.d.ts

@@ -1,7 +1,7 @@
 /**
  * Per-deployment row in {@link ListDeploymentsSuccess.deployments}. Mirrors
- * the 10 SDK fields the CLI emits; string-enums widened to `string` so the
- * published `.d.ts` stays off the SDK's const-enum types.
+ * the SDK fields the CLI emits; string-enums widened to `string`/`string[]`
+ * so the published `.d.ts` stays off the SDK's const-enum types.
  */
 export interface DeploymentSummary {
     key: string;
@@ -9,11 +9,21 @@ export interface DeploymentSummary {
     name: string;
     packageName: string;
     packageVersion: string;
+    /** Version the deployment currently runs. Absent until a version is installed. */
+    currentPackageVersion?: string | null;
+    /** Version a pending in-place upgrade targets. Differs from `currentPackageVersion` when an upgrade is queued. */
+    targetPackageVersion?: string | null;
+    /** A newer published version, when one exists — the upgrade the deployment can move to. */
+    newPackageVersionAvailable?: string | null;
+    /** The last/pending deployment operation (e.g. `Install`, `VersionChange`). */
+    operation: string;
     operationStatus: string;
     activationStatus: string;
     folderPath?: string | null;
     installedRootFolderKey?: string | null;
     deploymentCreationTime: Date;
+    /** Pending workflow actions (e.g. `Upgrade`) — a queued in-place upgrade shows `["Upgrade"]`. */
+    actions: string[];
 }
 export type ListDeploymentsFailureReason = "auth_failed" | "folder_resolution_failed" | "list_request_failed";
 /** Local mirror of solution-sdk's `OrderByDirection`; declared here so the `.d.ts` stays off the SDK type. */
@@ -35,6 +45,18 @@ export interface ListDeploymentsOptions {
     sortBy?: string;
     /** Sort direction. Default `"Descending"`. */
     sortOrder?: SortDirection;
+    /**
+     * Filter to these deployment operation statuses (e.g. `"InProgress"`).
+     * Sent to the search request's `operationStatuses` array — filters
+     * server-side, unlike {@link folderPath}.
+     */
+    operationStatuses?: string[];
+    /**
+     * Filter to these deployment activation statuses (e.g. `"Active"`).
+     * Sent to the search request's `activationStatuses` array — filters
+     * server-side, unlike {@link folderPath}.
+     */
+    activationStatuses?: string[];
     /** Minimum minutes before token expiration to trigger a refresh. Default 10. */
     loginValidity?: number;
 }

package/dist/services/deploy-run-service.d.ts

@@ -2,6 +2,12 @@
 export type DeployFailureReason = "auth_failed" | "folder_resolution_failed" | "config_file_not_found" | "config_file_read_failed" | "config_file_parse_failed" | "install_request_failed"
 /** Personal Workspace deploy via AS auto-deploy failed (publish first, then retry). */
  | "personal_workspace_deploy_failed"
+/**
+ * Redeploy blocked: a deployment for this solution already exists (HTTP 400
+ * "Deployment exists in a failed or running state") and must be upgraded in
+ * place instead of redeployed.
+ */
+ | "deployment_exists"
 /** Recovery: deployment completed but flagged "Needs Setup" — manual config required before activation. */
  | "needs_setup_to_activate"
 /** Recovery: deployment completed, ready to activate — auto-activation didn't run. */

package/dist/services/deployment-search.d.ts

@@ -1,5 +1,5 @@
 import type { PipelineDeploymentResult, PipelineDeploymentStatus } from "@uipath/pipelines-sdk";
-import type { DeploymentOperationStatus, DeploymentSearchItemDto2 } from "@uipath/solution-sdk";
+import type { DeploymentOperationStatus, DeploymentSearchItemDto2, InitOverrideFunction } from "@uipath/solution-sdk";
 import type { SolutionAuthContext } from "./auth-helper";
 /**
  * Look up a deployment by name in the persistent search/list service.
@@ -10,6 +10,14 @@ import type { SolutionAuthContext } from "./auth-helper";
  * when you want a best-effort lookup that swallows failures.
  */
 export declare function findDeploymentByName(auth: SolutionAuthContext, deploymentName: string): Promise<DeploymentSearchItemDto2 | undefined>;
+/**
+ * Best-effort lookup of the deployment that blocks a redeploy of `packageName`.
+ * Pages `searchSearchDeployments22` by substring like {@link findDeploymentByName},
+ * then returns the first row whose `packageName` matches exactly (and, when
+ * `folderPath` is given, whose `folderPath` matches too). Swallows any lookup
+ * failure and returns undefined so the caller's original error always surfaces.
+ */
+export declare function findDeploymentByPackageName(auth: SolutionAuthContext, packageName: string, folderPath?: string, scope?: InitOverrideFunction): Promise<DeploymentSearchItemDto2 | undefined>;
 /**
  * Best-effort lookup for use in error-handling paths — returns undefined on
  * any failure instead of propagating, so it never masks the original error.

package/dist/services/entry-point-spec-enhancer.d.ts

@@ -3,7 +3,7 @@ import type { IArtifactResourceSpecEnhancer, ISolutionContext, ResourceDefinitio
 /**
  * Reads the project's `entry-points.json` at GET time and projects the primary
  * entry points onto the resource spec, so consumers see the current on-disk
- * state — not the snapshot captured at `solution project add`.
+ * state — not the snapshot captured at `solution projects add`.
  *
  * Mirrors the shape Studio Web returns from its process configuration
  * endpoint: `entryPoints` always carries the raw `entry-points.json` text;

package/dist/services/local-resource-matcher.d.ts

@@ -0,0 +1,27 @@
+import type { ResourceDefinition } from "@uipath/resource-builder-sdk";
+/**
+ * Pure, dependency-free matching primitives for local solution resources.
+ * A leaf module on purpose: `sync-resources-from-bindings` and
+ * `resource-mutations` both re-export from here (so existing callers keep
+ * their import paths), while `commands/resource-add.ts` imports it directly —
+ * which lets its spec run the REAL matcher without mocking this module.
+ */
+/**
+ * Normalize a folder path for comparisons. `.` and `solution_folder` both
+ * encode "no folder" (tenant/root scope) — collapsing them to undefined lets
+ * us compare a binding's folder against an existing resource's folder
+ * consistently regardless of which placeholder either side carries.
+ */
+export declare function normalizeFolderPath(path: string | undefined): string | undefined;
+/**
+ * Find a solution resource matching (kind, name | name_<N>, normalized
+ * folder). Kind + name are compared case-insensitively; the suffix variants
+ * match because SDK's `addResourceWithUniqueName` may have suffixed an
+ * earlier add/import of the same name. With a solution-relative `folderPath`
+ * (`.` / `solution_folder` / undefined) only root-scope resources match.
+ *
+ * Single source of truth for "does an in-solution resource already cover
+ * this (kind, name, folder)?" — used by the refresh import guard (UV-15289),
+ * the virtual idempotency check, and `resources add --source local`.
+ */
+export declare function findMatchingLocalResource(resources: ResourceDefinition[], kind: string, name: string, folderPath: string | undefined): ResourceDefinition | undefined;

package/dist/services/pack-command-service.d.ts

@@ -18,6 +18,14 @@ export declare class PackCommandService {
      * Execute the pack command and return result (for programmatic usage and testing)
      */
     executeAsync(solutionPath: string, options: PackCommandOptions): Promise<ToolResult>;
+    /**
+     * Find the member project directory that is equal to or contains the
+     * resolved output path, if any. Manifest read errors are ignored here —
+     * the packager reports them with full context later.
+     */
+    private findMemberProjectCollision;
+    private isPathEqualOrInside;
+    private readMemberProjectDirs;
     private prepareSolutionDirectoryForPack;
     private ensurePackagerAsync;
     private createPackOptions;

package/dist/services/project-artifacts-service.d.ts

@@ -0,0 +1,34 @@
+export interface AddProjectArtifactsOptions {
+    /** Absolute path to the solution directory (containing the `.uipx`). */
+    solutionDir: string;
+    /** Stable project key — must match the `Id` in `.uipx` `Projects[]`. */
+    projectId: string;
+    /** Display name for the project; typically the project folder name. */
+    projectName: string;
+    /**
+     * Project type as written to `project.uiproj` (e.g. `Flow`,
+     * `ProcessOrchestration`, `Agent`, `CaseManagement`). Normalized internally
+     * via `normalizeProjectType` so callers can pass the raw value.
+     */
+    projectType: string;
+}
+export interface ProjectArtifactsResult {
+    /** True when artifact resources were generated. */
+    Created: boolean;
+    /** Error message when `Created` is `false`. */
+    Error?: string;
+}
+/**
+ * Generate `resources/solution_folder/process/<kind>/` artifact-resource
+ * entries for a project that has just been registered in the parent
+ * solution's `.uipx`. Mirrors the second half of `uip solution project add`
+ * (after the manifest write), so `*-tool init` paths can produce the same
+ * complete on-disk state without requiring a follow-up
+ * `solution project remove` + `add` cycle.
+ *
+ * Returns a result envelope instead of throwing: the project files have
+ * already been created by the init caller, so a failure here is recoverable
+ * with `solution project remove` + `add`. Callers surface the result in
+ * their success envelope as `Data.ProjectArtifacts`.
+ */
+export declare function addProjectArtifactsToSolutionAsync(options: AddProjectArtifactsOptions): Promise<ProjectArtifactsResult>;

package/dist/services/sync-resources-from-bindings.d.ts

@@ -17,13 +17,7 @@ interface ResolvedKindMetadata {
      */
     requiredDefaults: RequiredPropertyDefault[];
 }
-/**
- * Normalize a folder path for comparisons. `.` and `solution_folder` both
- * encode "no folder" (tenant/root scope) — collapsing them to undefined lets
- * us compare a binding's folder against an existing resource's folder
- * consistently regardless of which placeholder either side carries.
- */
-export declare function normalizeFolderPath(path: string | undefined): string | undefined;
+export { findMatchingLocalResource, normalizeFolderPath, } from "./local-resource-matcher";
 interface SyncResult {
     created: number;
     imported: number;
@@ -137,4 +131,3 @@ export declare function readUipxProjects(solutionDir: string): Promise<UipxProje
  * on failure and continues. Used by pack and upload before packaging.
  */
 export declare function syncAndLog(solutionDir: string): Promise<void>;
-export {};

package/dist/templates/AGENTS.md

@@ -1,6 +1,6 @@
 # UiPath Solution Workspace
 
-> **A `.uipx` file in this directory marks a UiPath solution. Drive every solution operation through the `uip` CLI — packing, publishing, deploying, and deployment configuration.** Do not hand-edit `.uipx`; manage projects via `uip solution project ...` so the manifest stays internally consistent.
+> **A `.uipx` file in this directory marks a UiPath solution. Drive every solution operation through the `uip` CLI — packing, publishing, deploying, and deployment configuration.** Do not hand-edit `.uipx`; manage projects via `uip solution projects ...` so the manifest stays internally consistent.
 
 This file is a static snapshot, scaffolded by the `uip` CLI version `{{cli_version}}`. If the CLI version you have access to is different, there may be inconsistencies in the commands or options listed below. When you encounter one, look up the current form with `uip <group> --help` and **edit this file in place** — find and replace the stale command with the working one.
 
@@ -44,10 +44,10 @@ You must manage membership via the CLI, never by editing the manifest. All these
 | Intent | Command |
 |---|---|
 | Create a solution | `uip solution init <name>` |
-| Register an existing subfolder of the solution dir as a project (no copying — use after scaffolding *inside* the solution dir, e.g. `uip rpa create-project --location <solution-dir>`) | `uip solution project add <project-path> [<solution-file>]` |
-| Add a project from outside the solution — copies the folder at `<path>` into the solution dir and registers it (`<path>` is a local filesystem path) | `uip solution project import <path>` |
-| Unregister a project (does not delete the project files on disk) | `uip solution project remove <project-path> [<solution-file>]` |
-| List projects in the solution | `uip solution project list` |
+| Register an existing subfolder of the solution dir as a project (no copying — use after scaffolding *inside* the solution dir, e.g. `uip rpa create-project --location <solution-dir>`) | `uip solution projects add <project-path> [<solution-file>]` |
+| Add a project from outside the solution — copies the folder at `<path>` into the solution dir and registers it (`<path>` is a local filesystem path) | `uip solution projects import <path>` |
+| Unregister a project (does not delete the project files on disk) | `uip solution projects remove <project-path> [<solution-file>]` |
+| List projects in the solution | `uip solution projects list` |
 
 The `uip ... init` scaffolders (`agent init`, `maestro flow init`, `maestro bpmn init`, `maestro case init`, `api-workflow init`) **auto-register** the new project when run inside a solution directory — they walk up for the enclosing `.uipx` and add it to `Projects[]` automatically, so a separate `project add` is not needed. Pass `--skip-solution-registration` to scaffold standalone without registering; the output's `Data.SolutionRegistration.Status` is then `OptedOut`. The full set of `Status` values is: `Registered` / `AlreadyRegistered` (added in this run / already present), `NotInSolution` (no enclosing `.uipx` found), `OptedOut` (`--skip-solution-registration` passed), `Skipped` (a candidate solution was found but registration was not safe to attempt — e.g. multiple `.uipx` in one directory, or the project sits outside the solution dir), and `Failed` (manifest read/parse/write error).
 
@@ -72,7 +72,7 @@ A solution can contain multiple projects of different types. The table below lis
 
 All skill should be installed by running the command: `uip skills install`. The general-purpose `uipath-platform` skill covers what isn't in a type-specific skill.
 
-The type lives in either `project.uiproj` (top-level `ProjectType`) or `project.json` (`designOptions.outputType`, falling back to top-level `ProjectType` when `outputType` is absent — read or write either field). The `init` scaffolders above auto-register when run inside a solution directory (unless `--skip-solution-registration` is passed). For other scaffolders, register the project with the solution after scaffolding: use `uip solution project add <project-path> [<solution-file>]` when the project already lives inside the solution directory (registers in place, no copy), or `uip solution project import <path>` to copy a project from outside the solution dir into it and register it. If you pass an unknown type to those commands, they reject with the exhaustive accepted list — trust that error over this table.
+The type lives in either `project.uiproj` (top-level `ProjectType`) or `project.json` (`designOptions.outputType`, falling back to top-level `ProjectType` when `outputType` is absent — read or write either field). The `init` scaffolders above auto-register when run inside a solution directory (unless `--skip-solution-registration` is passed). For other scaffolders, register the project with the solution after scaffolding: use `uip solution projects add <project-path> [<solution-file>]` when the project already lives inside the solution directory (registers in place, no copy), or `uip solution projects import <path>` to copy a project from outside the solution dir into it and register it. If you pass an unknown type to those commands, they reject with the exhaustive accepted list — trust that error over this table.
 
 ## End-to-End Lifecycle
 
@@ -156,7 +156,7 @@ uip solution delete <solution-id> --yes    # remove a solution from Studio Web (
 
 Each project declares the resources it needs (assets, queues, buckets, processes, …) in a `bindings_v2.json` file at the project root. These declarations drive the solution's resource inventory.
 
-After editing a project's bindings, or after `solution project import` (which doesn't auto-sync resources), reconcile the solution-level inventory:
+After editing a project's bindings, or after `solution projects import` (which doesn't auto-sync resources), reconcile the solution-level inventory:
 
 ```bash
 uip solution resources refresh     # re-scan every project, sync new / removed resources