@uipath/solution-tool 1.196.0 → 1.197.0-preview.59

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

@@ -19,6 +19,5 @@ export declare class PackCommandService {
      */
     executeAsync(solutionPath: string, options: PackCommandOptions): Promise<ToolResult>;
     private ensurePackagerAsync;
-    private readFileAsUint8Array;
     private createPackOptions;
 }

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

@@ -1,13 +1,3 @@
-import "@uipath/packager-tool-apiworkflow";
-import "@uipath/packager-tool-bpmn";
-import "@uipath/packager-tool-case";
-import "@uipath/packager-tool-connector";
-import "@uipath/packager-tool-flow";
-import "@uipath/packager-tool-functions";
-import "@uipath/packager-tool-webapp";
-import "@uipath/packager-tool-workflowcompiler";
-import "@uipath/resource-builder-tool";
-import "@uipath/tool-agent";
 import type { PackCommandOptions } from "../models/pack-command-types";
 export type { PackCommandOptions };
 /**

package/dist/services/solution-packager-helpers.d.ts

@@ -0,0 +1,25 @@
+import type { IFileSystem } from "@uipath/filesystem";
+import { type ISolutionPackager, type SolutionPackOptions } from "@uipath/solution-packager/node";
+import { LogLevel } from "@uipath/solutionpackager-tool-core";
+/**
+ * Shared building blocks for the solution packager command services
+ * (`pack`, `restore`). Both run the same SDK packager with the same auth
+ * connection and log-level mapping; keeping that logic here avoids duplicating
+ * it across the per-command services.
+ */
+/** Create a node solution packager wired to the CLI logger and telemetry. */
+export declare function createSolutionPackager(): Promise<ISolutionPackager>;
+/**
+ * Read a solution file as a `Uint8Array`. `IFileSystem.readFile` may hand back
+ * a `Buffer`/array depending on the backend, so coerce it before passing the
+ * bytes to the packager.
+ */
+export declare function readSolutionFileAsUint8Array(fs: IFileSystem, filePath: string): Promise<Uint8Array>;
+/** Map the CLI logger level to the packager SDK log level (defaults to Error). */
+export declare function resolveSdkLogLevel(): LogLevel;
+/**
+ * Attach the authenticated cloud connection to the packager options when a
+ * session is available. No-op when the user is not logged in (the packager
+ * then runs against public feeds only).
+ */
+export declare function applyAuthConnection(options: SolutionPackOptions, loginValidity?: number): Promise<void>;

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

@@ -66,6 +66,14 @@ export interface RcsMatch {
         path?: string;
     };
 }
+/**
+ * Find a resource in RCS by key (UUID). RCS's `SearchFolderEntities` endpoint
+ * has no key-based filter — only `name`/`entityTypes`/`entitySubTypes`. We
+ * paginate all resources of this kind and filter locally by key, exiting
+ * early on the match. Used for connections, whose binding carries the UUID
+ * directly via `bindingKey`.
+ */
+export declare function findResourceByKeyInRcs(builder: ISolutionBuilder, kind: string, expectedKey: string, folderPath?: string, propagateErrors?: boolean): Promise<RcsMatch | undefined>;
 /**
  * Page through RCS for a given (kind, name) and collect every match. Returns
  * an empty array on lookup error (logged as a warning). Callers decide what

package/dist/templates/AGENTS.md

@@ -49,7 +49,7 @@ You must manage membership via the CLI, never by editing the manifest. All these
 | 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` |
 
-The `uip ... init` scaffolders (`agent init`, `maestro flow init`, `maestro bpmn init`, `maestro case 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).
+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).
 
 ## Project Types
 
@@ -66,7 +66,7 @@ A solution can contain multiple projects of different types. The table below lis
 | `Agent` | LLM agent project — **low-code** (configured via `agent.json`; no Python) or **coded** (Python: LangGraph / LlamaIndex / OpenAI Agents). Both subtypes share `ProjectType: "Agent"`; the discriminator is `agent.json#type`. | `uip agent init <path>` (low-code) · `uip codedagent new [name]` (coded — see the `uipath-agents` skill for the full flow) | `uipath-agents` |
 | `AppV2` | Coded App — web application | `uip codedapp init <path>` | `uipath-coded-apps` |
 | `Function` | UiPath Function (JS / TS / Python) | `uip functions new [name]` | none |
-| `Api` | API Workflow project | no CLI scaffolding | none |
+| `Api` | API Workflow project | `uip api-workflow init <name>` | none |
 | `Connector` | Integration Service connector | no CLI scaffolding — use `uip is connectors` to list / get / export existing connectors | none |
 | `WebApp` | Legacy low-code UiPath App (the coded variant is `AppV2`) | no CLI scaffolding | none |
 
@@ -85,6 +85,13 @@ uip login
 #    Non-interactive (CI / CD) with client credentials:
 uip login --client-id <ID> --client-secret <SECRET> --tenant <TENANT>
 
+# 1a. (Optional) Restore project dependencies before packing. Resolves NuGet
+#     deps (including authenticated Orchestrator feeds) so pack can compile.
+#     Useful in CI: login -> restore -> pack. Takes <solutionPath> only; it
+#     does not produce a package. Pack also restores internally, so this is an
+#     optimization, not a requirement.
+uip solution restore .
+
 # 2. Pack the solution into a .zip. Two positional args:
 #    <solutionPath>  — solution dir (containing .uipx) or a .uis file
 #    <output-path>   — directory where the .zip is written (required unless --dry-run)
@@ -128,6 +135,10 @@ uip solution deploy uninstall <deployment-name> --yes   # remove the deployment
 
 `uninstall` and `activate` take the deployment name as a **positional** argument (no `--name` flag). `status` takes the **pipeline deployment ID** (the GUID returned by `deploy run`), also positional.
 
+## Package Signing
+
+`solution pack` can sign each packed project `.nupkg` with a code-signing certificate. Signing is opt-in: add `--signing-certificate-path <cert.pfx>` to the pack command. The certificate password (`--signing-certificate-password`) is optional — passing it as `env.VAR` (e.g. `env.SIGNING_PASSWORD`) is recommended, though an inline value also works. An optional timestamp server is set with `--signing-timestamp-server <url>`.
+
 ## Studio Web (Browser Editing)
 
 Studio Web is a separate target from the Orchestrator deploy chain — it hosts a browser-based collaborative editor for solutions. The `solution upload` command pushes the local solution there and returns a `DesignerUrl` to open the solution in a browser; this is independent of `pack` / `publish` / `deploy` and does *not* produce a runtime-deployable artifact.
@@ -198,6 +209,8 @@ The CLI talks about the same resource types Orchestrator does:
 - **Connections** — Integration Service connections to external systems (Salesforce, ServiceNow, …).
 - **Processes / Releases** — published packages bound to a folder.
 - **Triggers** & **Webhooks** — event-, time-, or queue-based job firing; outbound HTTP notifications.
+- **Entities** — Data Service tables. Add or bind with kind `Entity`.
+- **ChoiceSets** — enumerations used by entity fields. Add with kind `ChoiceSet`.
 
 Resources outside a solution are managed under the orchestrator tool, which exposes per-type subgroups (`uip or assets …`, `uip or queues …`, `uip or buckets …`, `uip or bucket-files …`, `uip or libraries …`, `uip or queue-items …`, `uip or triggers …`, `uip or webhooks …`). Run `uip or --help` for the live list. Example: