@uipath/solution-tool 1.205.0-preview.277 → 1.206.0-preview.279

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (132) hide show
  1. package/dist/{archive-extract-x35t9ktj.js → archive-extract-136rn3ja.js} +13 -15
  2. package/dist/{cleanup-command-service-dwbrt6d9.js → cleanup-command-service-ejakyhea.js} +34 -31
  3. package/dist/deploy-delete-service-r7abfh28.js +23 -0
  4. package/dist/deploy-run-service-rnthz10q.js +23 -0
  5. package/dist/{deploy-status-service-xw2nzh7m.js → deploy-status-service-6my5vm61.js} +72 -62
  6. package/dist/deploy.js +35 -37
  7. package/dist/deployment-search-gfm907tx.js +54 -0
  8. package/dist/{embedded-file-reader-z4becc02.js → embedded-file-reader-0228j82a.js} +1 -4
  9. package/dist/feed-resolver-14crsx5y.js +27 -0
  10. package/dist/feed-scope-failure-67cyybn0.js +20 -0
  11. package/dist/feed-session-g94q2bjc.js +23 -0
  12. package/dist/first-party-service-n3vva2m4.js +8 -0
  13. package/dist/governance-options-t20vsznh.js +19 -0
  14. package/dist/index-aspmac9f.js +24 -0
  15. package/dist/index-ddk6v1ej.js +60 -0
  16. package/dist/{index-sby22td6.js → index-nzr4mx5p.js} +2 -22
  17. package/dist/index-qq4kre7a.js +93 -0
  18. package/dist/index-t262f2xv.js +16 -0
  19. package/dist/index.js +33 -34
  20. package/dist/init.js +18 -21
  21. package/dist/{jmespath-231m3hyn.js → jmespath-ab6tdc42.js} +1 -1
  22. package/dist/{js-yaml-88tdqrtd.js → js-yaml-a2bk27p6.js} +1 -3
  23. package/dist/{list-zckdhv0c.js → list-jntan9tx.js} +23 -23
  24. package/dist/models/pack-command-types.d.ts +3 -1
  25. package/dist/node-kwzcw5ex.js +25 -0
  26. package/dist/pack-command-service-pwaeha7y.js +29 -0
  27. package/dist/{pack-project-erd95bt1.js → pack-project-ztt1hfrs.js} +33 -40
  28. package/dist/pack.js +26 -30
  29. package/dist/package-id-4tsg5jsb.js +11 -0
  30. package/dist/{packager-tool-d3cmmbw1.js → packager-tool-1bz9h5ca.js} +11 -11
  31. package/dist/{packager-tool-gs3f3tf7.js → packager-tool-1ctvbx0h.js} +1 -1
  32. package/dist/{packager-tool-r1jvvm8y.js → packager-tool-55ztfccd.js} +176 -196
  33. package/dist/{packager-tool-wrg41m7t.js → packager-tool-95y24705.js} +37 -39
  34. package/dist/{packager-tool-bkjqza3a.js → packager-tool-9j8e5q1z.js} +184 -33
  35. package/dist/{packager-tool-tx834spe.js → packager-tool-9vrwpgt3.js} +757 -309
  36. package/dist/packager-tool-a6va4gc5.js +1178 -0
  37. package/dist/{packager-tool-pbmqk39a.js → packager-tool-a7s0gbxs.js} +33 -28
  38. package/dist/{packager-tool-47wzvqw0.js → packager-tool-aws5w512.js} +6 -6
  39. package/dist/{packager-tool-97rcgwvv.js → packager-tool-bs1jn1yn.js} +331 -55
  40. package/dist/packager-tool-c64hqa8n.js +106 -0
  41. package/dist/{packager-tool-5ddtwzva.js → packager-tool-ca5ngmqv.js} +12 -12
  42. package/dist/{packager-tool-6kz1pv9f.js → packager-tool-d1texmvn.js} +828 -338
  43. package/dist/{packager-tool-1de529jm.js → packager-tool-epsr41wx.js} +12 -3
  44. package/dist/packager-tool-f84z7nds.js +130 -0
  45. package/dist/{packager-tool-8ptbmmmp.js → packager-tool-fp46ebde.js} +147 -76
  46. package/dist/packager-tool-fqs6hdcy.js +290 -0
  47. package/dist/{packager-tool-3bwnkjdq.js → packager-tool-fx4ws49n.js} +12 -12
  48. package/dist/{packager-tool-6ybywxxn.js → packager-tool-m07vyk89.js} +371 -221
  49. package/dist/{packager-tool-hsya909c.js → packager-tool-nrhqgr4z.js} +273 -255
  50. package/dist/{packager-tool-61pwb567.js → packager-tool-ppj5f4y7.js} +6 -7
  51. package/dist/{packager-tool-qqbt4b44.js → packager-tool-pyt9fvty.js} +51 -48
  52. package/dist/packager-tool-q5d9df2q.js +74 -0
  53. package/dist/{packager-tool-ph7fg1aa.js → packager-tool-q8ryk6q9.js} +122 -89
  54. package/dist/{packager-tool-t8gh825q.js → packager-tool-qf8753ee.js} +53 -41
  55. package/dist/{packager-tool-60af1hw2.js → packager-tool-qzcd5c9s.js} +3 -3
  56. package/dist/packager-tool-resolver-td3bhccd.js +20 -0
  57. package/dist/{packager-tool-dfrk01gn.js → packager-tool-rj2d1g0w.js} +154 -154
  58. package/dist/{packager-tool-a4bs7wtm.js → packager-tool-snm6s7b5.js} +15 -15
  59. package/dist/{packager-tool-43ahv5mn.js → packager-tool-t39pjz7n.js} +35 -18
  60. package/dist/{packager-tool-f2hsb9ta.js → packager-tool-t3a48ys5.js} +305 -657
  61. package/dist/{packager-tool-cjjk2ek2.js → packager-tool-t3ahzjh1.js} +356 -298
  62. package/dist/{packager-tool-v1f5e8t9.js → packager-tool-vgrswa8p.js} +53 -8
  63. package/dist/packager-tool-vrtabg73.js +2307 -0
  64. package/dist/{packager-tool-gmwva4yv.js → packager-tool-vx2c68sb.js} +2 -2
  65. package/dist/{packager-tool-4pkzxkty.js → packager-tool-vx39dhvn.js} +65 -35
  66. package/dist/{packager-tool-zn76tbxc.js → packager-tool-w34wyhwf.js} +13 -15
  67. package/dist/packager-tool-w8bcwfd3.js +280 -0
  68. package/dist/{packager-tool-3gwrcgrc.js → packager-tool-wm0h0wa1.js} +18 -18
  69. package/dist/{packager-tool-b2nhscfk.js → packager-tool-wm8nj6e9.js} +18 -18
  70. package/dist/{packager-tool-amhyxzz6.js → packager-tool-x33sdw6n.js} +16 -16
  71. package/dist/{packager-tool-wy4fx250.js → packager-tool-yetmzme9.js} +89 -30
  72. package/dist/{packager-tool-6tyyvhh0.js → packager-tool-z5r49ky9.js} +75 -9
  73. package/dist/packager-tool.js +6 -7
  74. package/dist/prepare-solution-resources-pwnyvtza.js +26 -0
  75. package/dist/{project-command-utils-t6pmpvq3.js → project-command-utils-zcmbecfy.js} +23 -26
  76. package/dist/project-contributions-kh9yftvg.js +27 -0
  77. package/dist/publish.js +17 -17
  78. package/dist/resource-mutations-mfn5k1hb.js +27 -0
  79. package/dist/{resource-version-lookup-0e3e2j58.js → resource-version-lookup-6ejh1hwd.js} +20 -23
  80. package/dist/resource.js +13 -16
  81. package/dist/{restore-command-service-2g02d7s1.js → restore-command-service-n880dxre.js} +37 -34
  82. package/dist/{run-service-6necpy9s.js → run-service-4vhn6mtb.js} +144 -66
  83. package/dist/services/deploy-activate-service.d.ts +2 -1
  84. package/dist/services/deployment-search-client.d.ts +2 -1
  85. package/dist/services/deployment-search.d.ts +39 -0
  86. package/dist/services/feed-resolver.d.ts +13 -1
  87. package/dist/services/feed-selection.d.ts +8 -5
  88. package/dist/services/feed-session.d.ts +34 -0
  89. package/dist/services/install-run.d.ts +92 -0
  90. package/dist/services/prepare-solution-resources.d.ts +11 -2
  91. package/dist/services/project-contributions.d.ts +2 -0
  92. package/dist/services/project-identity-telemetry.d.ts +3 -0
  93. package/dist/services/publish-service.d.ts +20 -3
  94. package/dist/services/solution-identity.d.ts +18 -0
  95. package/dist/ship-telemetry-bkf3800w.js +16 -0
  96. package/dist/solution-auth-jxcgd2m0.js +10 -0
  97. package/dist/solution-identity-92h2fbpa.js +19 -0
  98. package/dist/templates/AGENTS.md +27 -29
  99. package/dist/tool.js +32 -33
  100. package/package.json +2 -2
  101. package/dist/deploy-delete-service-7py597ng.js +0 -25
  102. package/dist/deploy-run-service-446bssn0.js +0 -25
  103. package/dist/deployment-search-qyd6dv0m.js +0 -55
  104. package/dist/feed-resolver-va10c73n.js +0 -28
  105. package/dist/feed-scope-failure-3yxfg1x7.js +0 -19
  106. package/dist/feed-session-7xqphdrg.js +0 -17
  107. package/dist/first-party-service-sd8yaf73.js +0 -27
  108. package/dist/governance-options-8snbrbt1.js +0 -32
  109. package/dist/index-dqa169gp.js +0 -25
  110. package/dist/index-fcwmbjap.js +0 -667
  111. package/dist/index-prm27bvm.js +0 -138
  112. package/dist/node-9hdy9st1.js +0 -86
  113. package/dist/pack-command-service-tr3z33gz.js +0 -35
  114. package/dist/package-id-kdkapmn2.js +0 -13
  115. package/dist/packager-tool-53w8skv5.js +0 -262
  116. package/dist/packager-tool-5edvzz80.js +0 -543
  117. package/dist/packager-tool-6d3fx89p.js +0 -171
  118. package/dist/packager-tool-d8ng7mex.js +0 -68
  119. package/dist/packager-tool-gdtpsdn7.js +0 -342
  120. package/dist/packager-tool-mq5pc4zr.js +0 -418
  121. package/dist/packager-tool-qw47eyw7.js +0 -43
  122. package/dist/packager-tool-resolver-994z3jkj.js +0 -23
  123. package/dist/packager-tool-rg3xgn9a.js +0 -182
  124. package/dist/packager-tool-sxjehksx.js +0 -5367
  125. package/dist/packager-tool-yrdyppjd.js +0 -188
  126. package/dist/prepare-solution-resources-m1djfj62.js +0 -29
  127. package/dist/project-contributions-79ndycrx.js +0 -32
  128. package/dist/resource-mutations-c3krjqze.js +0 -36
  129. package/dist/ship-telemetry-myes7ak5.js +0 -21
  130. package/dist/solution-auth-aead70sw.js +0 -11
  131. /package/dist/{packager-tool-act5r386.js → packager-tool-2pxe2r4j.js} +0 -0
  132. /package/dist/{packager-tool-kkfb5kgn.js → packager-tool-vrqbbh01.js} +0 -0
@@ -0,0 +1,92 @@
1
+ import type { PollUntilResult } from "@uipath/common";
2
+ import type { PipelineDeploymentResult, PipelinesApi } from "@uipath/pipelines-sdk";
3
+ import type { InitOverrideFunction } from "@uipath/solution-sdk";
4
+ import type { SolutionAuthContext } from "@uipath/solution-sdk/auth";
5
+ import { type PermanentDeletionRefusal } from "./permanent-deletion-consent";
6
+ import { type PolledPipelineResult } from "./pipeline-deploy-poll";
7
+ /**
8
+ * One `pipelinesInstall` request: the install the caller wants, with its own
9
+ * request body and its own wording for a refusal. The install route is a
10
+ * unified install / upgrade / configuration change, so `deploy run` and
11
+ * `deploy upgrade` differ only in what they send and say.
12
+ */
13
+ export type InstallStep<F> = () => Promise<{
14
+ ok: true;
15
+ pipelineDeploymentId: string;
16
+ } | F>;
17
+ /** What an install step may fail with: the caller's own failure shape. */
18
+ export interface InstallFailure {
19
+ ok: false;
20
+ instructions: string;
21
+ }
22
+ export interface InstallRunRequest<F extends InstallFailure> {
23
+ api: PipelinesApi;
24
+ auth: SolutionAuthContext;
25
+ deploymentName: string;
26
+ scope: InitOverrideFunction | undefined;
27
+ signal: AbortSignal | undefined;
28
+ /** `--timeout`, already defaulted: bounds every poll of the run together. */
29
+ timeoutSeconds: number;
30
+ pollIntervalMs: number;
31
+ /** Prefix for the poll's progress lines, e.g. `"deploy upgrade"`. */
32
+ logPrefix: string;
33
+ /** `--no-wait`: stop once the server has accepted the install. */
34
+ noWait?: boolean;
35
+ /** `--acknowledge-permanent-deletion` was passed. */
36
+ acknowledge: boolean;
37
+ /** Sends the install. Called again, identically, after an acknowledgement. */
38
+ install: InstallStep<F>;
39
+ /**
40
+ * The caller's words for a permanent-deletion refusal. Takes the refused
41
+ * status because the retry commands it prints may name its draft key.
42
+ */
43
+ consentWording: (refused: PipelineDeploymentResult) => {
44
+ verb: string;
45
+ confirmHint: string;
46
+ keepCopiesHint: string;
47
+ };
48
+ }
49
+ export type InstallRunOutcome<F> = {
50
+ /** `noWait`: the install was accepted and nothing was polled. */
51
+ kind: "accepted";
52
+ pipelineDeploymentId: string;
53
+ } | {
54
+ /** A run reached the end of its poll; the caller reads the status. */
55
+ kind: "polled";
56
+ pipelineDeploymentId: string;
57
+ pollResult: PollUntilResult<PolledPipelineResult>;
58
+ /** One entry per resource the re-run deleted, when consent was given. */
59
+ permanentlyDeletedResources: string[] | undefined;
60
+ } | {
61
+ /** The server refused an install request before any run existed. */
62
+ kind: "install_refused";
63
+ failure: F;
64
+ } | {
65
+ /** The run stopped for a permanent-deletion confirmation it did not get. */
66
+ kind: "consent_refused";
67
+ refusal: PermanentDeletionRefusal;
68
+ pipelineDeploymentId: string;
69
+ deploymentKey: string | undefined;
70
+ };
71
+ /** `value` when it is a finite number (0 included), else `fallback`. */
72
+ export declare function finiteOr(value: number | undefined, fallback: number): number;
73
+ /**
74
+ * Run an install to the end of its pipeline: install, poll, and — when the
75
+ * server stops for permanent-deletion consent — settle the consent and re-run
76
+ * the same install once.
77
+ *
78
+ * One deadline covers every poll, set when the first one starts, so
79
+ * `--timeout` bounds the whole wait even when the install runs twice. A second
80
+ * refusal after consent is final: the run never loops.
81
+ *
82
+ * With `noWait` it stops after the one install the server accepted.
83
+ *
84
+ * Reading the final status is the caller's: `deploy run` recovers and
85
+ * activates states that `deploy upgrade` never sees.
86
+ */
87
+ export declare function runInstallToOutcomeAsync<F extends InstallFailure>(request: InstallRunRequest<F> & {
88
+ noWait?: false;
89
+ }): Promise<Exclude<InstallRunOutcome<F>, {
90
+ kind: "accepted";
91
+ }>>;
92
+ export declare function runInstallToOutcomeAsync<F extends InstallFailure>(request: InstallRunRequest<F>): Promise<InstallRunOutcome<F>>;
@@ -1,5 +1,5 @@
1
1
  import type { IFileSystem } from "@uipath/filesystem";
2
- import { type ContributedBinding } from "@uipath/solution-sdk/resources";
2
+ import { type ContributedBinding, type SelfProvisionedResource } from "@uipath/solution-sdk/resources";
3
3
  import { type ProjectContributions } from "./project-contributions";
4
4
  export interface PrepareResult {
5
5
  /** Contributed problems (when not gating), skips, and unmatched patches. */
@@ -20,6 +20,13 @@ export declare function projectSubTypesFrom(contributions: ProjectContributions)
20
20
  * place of the project's `bindings_v2.json` file.
21
21
  */
22
22
  export declare function projectBindingsFrom(contributions: ProjectContributions): ReadonlyMap<string, readonly ContributedBinding[]>;
23
+ /**
24
+ * The resources the projects' tools define by name (`ProjectSpecPatch.name`):
25
+ * the solution provisions these itself, so the sync mints them without a
26
+ * Resource Catalog lookup. A case role is one; a logged-out pack of a case
27
+ * with roles packs because of this.
28
+ */
29
+ export declare function selfProvisionedFrom(contributions: ProjectContributions): SelfProvisionedResource[];
23
30
  /**
24
31
  * Bring a solution directory's resource JSONs in line with its projects'
25
32
  * authored files. Every path that reads those resources for real — `pack`,
@@ -36,7 +43,9 @@ export declare function projectBindingsFrom(contributions: ProjectContributions)
36
43
  * 4. sync — carries the contributed subTypes, which is what lets reconcile
37
44
  * generate (or repair) artefact resources for a type whose template row is
38
45
  * keyed `<type>_<subType>`, and the contributed bindings of a type that
39
- * keeps them in its own source format (a Flow's `.flow`).
46
+ * keeps them in its own source format (a Flow's `.flow`), and the
47
+ * name-targeted patches' resources, which it mints without asking the
48
+ * Resource Catalog.
40
49
  * 5. apply — after the sync, because the sync can create the app resource a
41
50
  * patch targets. An unmatched patch here is a contributor bug, not a race,
42
51
  * which is why gating callers also fail on one.
@@ -4,6 +4,8 @@ import { type ProjectContributionError, type ProjectResourceContribution } from
4
4
  export interface ProjectContributions {
5
5
  /** Per project key (the `.uipx` `Id`), what that project's factory returned. */
6
6
  byProject: Map<string, ProjectResourceContribution>;
7
+ /** Project name per key, for messages; a key with no entry is shown as is. */
8
+ names?: Map<string, string>;
7
9
  }
8
10
  export interface ApplyContributionsResult {
9
11
  /** Number of artefact resources whose spec was rewritten. */
@@ -0,0 +1,3 @@
1
+ import { type ProjectActivityObserver } from "@uipath/solutionpackager-tool-core";
2
+ /** One observer per invocation. Only projects actually reached get a row. */
3
+ export declare function createProjectActivityObserver(commandName: string): ProjectActivityObserver | undefined;
@@ -1,8 +1,16 @@
1
- import { type ErrorContext, type RetryHint } from "@uipath/common";
1
+ import { type CliErrorCode, type ErrorContext, type ProjectTelemetryCapture, type RetryHint } from "@uipath/common";
2
2
  import { type FeedScope } from "./feed-resolver";
3
3
  /** Discriminator for {@link PublishFailure}; library callers can ignore the tag and read `.message` / `.ok`. */
4
- export type PublishFailureReason = "auth_failed" | "file_not_found" | "not_a_zip" | "not_packed" | "project_package" | "file_read_failed" | "metadata_rewrite_failed" | "personal_workspace_resolution_failed" | "feed_resolution_failed" | "upload_failed" | "upload_rejected" | "upload_version_conflict" | "upload_network" | "poll_timeout" | "poll_failed" | "poll_aborted" | "publish_failed";
4
+ export type PublishFailureReason = "auth_failed" | "file_not_found" | "not_a_zip" | "not_packed" | "project_package" | "file_read_failed" | "metadata_rewrite_failed" | "personal_workspace_resolution_failed" | "feed_resolution_failed"
5
+ /**
6
+ * A feed publish under a session the server was not shown to honour there
7
+ * (an external app on a server that ignores the feed header): the version
8
+ * poll would read the tenant feed, so nothing is uploaded.
9
+ */
10
+ | "feed_requires_user_session" | "upload_failed" | "upload_rejected" | "upload_version_conflict" | "upload_network" | "poll_timeout" | "poll_failed" | "poll_aborted" | "publish_failed";
5
11
  export interface PublishOptions {
12
+ /** Optional command capture; reads identity from the buffer loaded for publishing. */
13
+ telemetryCapture?: ProjectTelemetryCapture;
6
14
  /** Override the active tenant for auth resolution. The CLI's deprecated `--tenant` flag flows through here. */
7
15
  tenant?: string;
8
16
  /** Pin auth to this exact `.uipath/.auth` path. */
@@ -63,8 +71,17 @@ export interface PublishFailure {
63
71
  * that table belongs to the service (SOL-7550).
64
72
  */
65
73
  errorCode?: string;
66
- /** Stable retry guidance from the shared classifier (upload failures only). */
74
+ /**
75
+ * The CLI's own `ErrorCode` for the envelope — not to be confused with
76
+ * {@link PublishFailure.errorCode}, the service's. Set for poll failures
77
+ * and for a feed the service classified (resolution or session refusal);
78
+ * emitted instead of the code the formatter infers from the message.
79
+ */
80
+ cliErrorCode?: CliErrorCode;
81
+ /** Stable retry guidance from the shared classifier (upload and poll failures). */
67
82
  retry?: RetryHint;
83
+ /** Instructions that replace the command's per-reason table when set. */
84
+ instructions?: string;
68
85
  /** Machine-readable context (httpStatus, service errorCode, requestId) for the envelope's `Context`. */
69
86
  context?: ErrorContext;
70
87
  }
@@ -0,0 +1,18 @@
1
+ import { type ProjectTelemetryCapture, type SolutionIdentityInput } from "@uipath/common";
2
+ /** Reuse publish's archive buffer; optional telemetry never changes publishing. */
3
+ export declare function capturePackedSolutionIdentity(capture: ProjectTelemetryCapture | undefined, bytes: Uint8Array): Promise<void>;
4
+ /**
5
+ * Read only native solution metadata from a solution folder or its `.uipx`;
6
+ * never search parent folders or write IDs. Archives are not read here: the
7
+ * commands that take one report the folder or bytes they already loaded.
8
+ */
9
+ export declare function readSolutionIdentity(target: string): Promise<SolutionIdentityInput>;
10
+ /**
11
+ * Report the folder the packager extracted a `.uis` into, so the request row
12
+ * carries the solution the command actually used. Await it before cleanup.
13
+ */
14
+ export declare function captureExtractedSolution(capture: ProjectTelemetryCapture | undefined, directory: string): Promise<void>;
15
+ /** Capture ids already selected by the upload handler, before temp cleanup. */
16
+ export declare function captureSolutionIdentity(capture: ProjectTelemetryCapture | undefined, id: string | undefined, previousId?: string): void;
17
+ /** Retain the selected registration even when the operation removes it. */
18
+ export declare function captureSolutionMember(capture: ProjectTelemetryCapture | undefined, memberId: string): void;
@@ -0,0 +1,16 @@
1
+ import {
2
+ summarizeShipProjectTypes2,
3
+ inspectSolutionPackageProjectTypes2,
4
+ trackSolutionShipSucceeded2
5
+ } from "./packager-tool-x33sdw6n.js";
6
+ import"./packager-tool-9vrwpgt3.js";
7
+ import"./packager-tool-m07vyk89.js";
8
+ import"./packager-tool-vgrswa8p.js";
9
+ import"./packager-tool-rj2d1g0w.js";
10
+ export {
11
+ inspectSolutionPackageProjectTypes2 as inspectSolutionPackageProjectTypes,
12
+ summarizeShipProjectTypes2 as summarizeShipProjectTypes,
13
+ trackSolutionShipSucceeded2 as trackSolutionShipSucceeded
14
+ };
15
+
16
+ //# debugId=CF42FC3389C4540A64756E2164756E21
@@ -0,0 +1,10 @@
1
+ import {
2
+ getSolutionAuthContext2
3
+ } from "./packager-tool-ppj5f4y7.js";
4
+ import"./packager-tool-t39pjz7n.js";
5
+ import"./packager-tool-vgrswa8p.js";
6
+ export {
7
+ getSolutionAuthContext2 as getSolutionAuthContext
8
+ };
9
+
10
+ //# debugId=D0318E126BDC065664756E2164756E21
@@ -0,0 +1,19 @@
1
+ import {
2
+ capturePackedSolutionIdentity2,
3
+ readSolutionIdentity2,
4
+ captureExtractedSolution2,
5
+ captureSolutionIdentity2,
6
+ captureSolutionMember2
7
+ } from "./packager-tool-f84z7nds.js";
8
+ import"./packager-tool-9vrwpgt3.js";
9
+ import"./packager-tool-m07vyk89.js";
10
+ import"./packager-tool-vgrswa8p.js";
11
+ export {
12
+ captureExtractedSolution2 as captureExtractedSolution,
13
+ capturePackedSolutionIdentity2 as capturePackedSolutionIdentity,
14
+ captureSolutionIdentity2 as captureSolutionIdentity,
15
+ captureSolutionMember2 as captureSolutionMember,
16
+ readSolutionIdentity2 as readSolutionIdentity
17
+ };
18
+
19
+ //# debugId=E4B03BBBFC78172A64756E2164756E21
@@ -153,13 +153,13 @@ uip solution deploy status <pipeline-deployment-id> # that run's progress and
153
153
  uip solution deploy list
154
154
  ```
155
155
 
156
- `deploy run` also takes `--parent-folder-key <key>` in place of `--parent-folder-path`, and `--personal-workspace` to deploy into your Personal Workspace instead of the tenant.
156
+ `deploy run` also takes `--parent-folder-key <key>` in place of `--parent-folder-path`, `--personal-workspace` to deploy into your Personal Workspace instead of the tenant, and `--feed <name-or-key>` to deploy a package published to another feed (see "Package Identity and Publishing").
157
157
 
158
158
  **Listing one folder's deployments.** `uip solution deploy list --folder-path <path>` (or `--folder-key <key>`) lists the deployments installed into that folder. The Solutions search does the filtering, so `--limit`, `--offset` and `Pagination.Total` all count matching deployments: page with `--offset <previous Offset + Returned>` while `Pagination.HasMore` is true. The match is on the folder's **full path** (`Shared/Finance`, not `Finance`), exact and not case-sensitive, and deployments in its subfolders are **not** included — list each subfolder with its own call. `FolderPath` is the folder the deployment was installed *into*; a row's `FolderKey` is the deployment's own solution folder one level below it, so passing that key to `--folder-key` matches no deployment — use the key of the `FolderPath` folder instead.
159
159
 
160
- **Every deploy waits, and validates first.** `deploy run` — tenant, `--personal-workspace` or `--feed` — goes through the Pipelines install, which validates the package against the target *before* it schedules the install, then polls the run to a terminal state and reports `Status: "DeploymentSucceeded"` with `DeploymentKey`, `PipelineDeploymentId` and `InstanceId`. A validation failure ends in `Status: ValidationFailed` with the per-resource errors in `Instructions`, and nothing is installed. `--timeout <seconds>` (default 360) bounds each polling phase; running out exits `2` with `ErrorCode: timeout` and `Retry: RetryLater` — "may still be running", so check `uip solution deploy status <pipeline-deployment-id>` rather than treating it as a failed install. `--wait` is accepted for backwards compatibility and does nothing. Deploying into a Personal Workspace or a folder feed needs a **user session**: under an external app's client-credentials token, `--personal-workspace` is refused before anything is requested and `--feed` is refused once it resolves to a feed other than the tenant feed (`ErrorCode: permission_denied`), because the server ignores the feed header on that token type and the install would otherwise land on the tenant feed under the requested name. A `--feed` that names the tenant feed is fine from CI/CD, as is omitting the flag. Reading a feed is the same: `deploy list` and `deploy status` with `--personal-workspace` or a folder-feed `--feed` refuse an external app (`ErrorCode: permission_denied`) instead of showing the tenant feed's records under that feed's name. A session whose kind cannot be read from its token is refused the same way; `uip login` records an interactive login as a user session.
160
+ **Every deploy waits, and validates first.** `deploy run` — tenant, `--personal-workspace` or `--feed` — goes through the Pipelines install, which validates the package against the target *before* it schedules the install, then polls the run to a terminal state and reports `Status: "DeploymentSucceeded"` with `DeploymentKey`, `PipelineDeploymentId` and `InstanceId`. A validation failure ends in `Status: ValidationFailed` with the per-resource errors in `Instructions`, and nothing is installed. `--timeout <seconds>` (default 360) bounds each polling phase; running out exits `2` with `ErrorCode: timeout` and `Retry: RetryLater` — "may still be running", so check `uip solution deploy status <pipeline-deployment-id>` rather than treating it as a failed install. A wait that stops early because the status reads keep failing exits `1` with the `ErrorCode` of that failure — `network_error` with `Retry: RetryLater` for a dropped connection — and the deploy may still be running, so check its status the same way before you run it again. `solution publish --wait` reports a failed wait the same way. On `deploy run`, `deploy activate`, `deploy uninstall`, `publish`, `projects publish` and `projects resync`, `--timeout` and `--poll-interval` take a whole number of 1 or more: `abc`, `1.5`, `0` or a negative number is refused before anything is sent (exit `3`, `ErrorCode: invalid_argument`), so there is no "no timeout" value. `--wait` is accepted for backwards compatibility and does nothing. **Folder feeds from CI/CD.** An external app (client-credentials login) can deploy into a folder feed with `--feed` only on a server that applies the feed to client-credentials requests. Before the first feed-scoped request the CLI asks the server once — a single-row search sent with the feed, on the route the command itself uses (the deployment search; the package search for `publish`, `packages list` and `packages delete`, so the question needs no scope the command does not), answered with an `X-UIPATH-FolderKey` echo on the response when the server ran it in that feed — and refuses (`ErrorCode: permission_denied`) when the echo is missing or the question fails, because an older server ignores the feed header on that token type and the install would land on the tenant feed under the requested name. `solution publish --feed` from an external app is guarded the same way and uploads nothing on such a server: the upload picks its feed by `locationKey`, but the `--wait` version read is scoped by the header alone and would read the tenant feed. The question is a read, so it needs that route's read scope next to the command's own: `Solutions.Packages.Read` for `publish`, `packages list` and `packages delete`, `Solutions.Deployments.Read` for the deploy verbs. An app holding only the write scope is refused by its own check, and the refusal names the read scope to add. The app's OAuth scope (`Solutions.Deployments`) is the whole authorization there: it reaches every folder feed in the tenant. Without a Studio Web (`StudioWebS2S`) grant an external app cannot list feeds (`solution feeds list` answers it with 401); then give `--feed` the feed's **folder key** or the path of the Orchestrator folder that owns the feed. A path is looked up through Orchestrator and needs the app's `OR.Folders` scope; a key is used as given, so `solution publish --feed <key>` needs no extra scope, while `deploy run --feed <key>` still reads the feed folder's path through Orchestrator (the install is addressed by path) and needs `OR.Folders` too — without it the deploy fails before anything is installed, with `ErrorCode: permission_denied` and instructions naming that scope. With the `StudioWebS2S` grant a feed name resolves through the listing as for a user. `--personal-workspace` is always refused to an external app, before anything is requested — an app has no Personal Workspace of its own. A `--feed` that names the tenant feed is fine from CI/CD, as is omitting the flag. Reading a feed follows the same rule: `deploy list` and `deploy status` with a folder-feed `--feed` work for an external app on such a server and are refused (`ErrorCode: permission_denied`) on an older one, instead of showing the tenant feed's records under that feed's name. A session whose kind cannot be read from its token is refused the same way; `uip login` records an interactive login as a user session.
161
161
 
162
- **Upgrading in place.** `uip solution deploy upgrade <deployment-key>` (the `Key` from `deploy list`) or `uip solution deploy upgrade --name <deployment-name> --package-name <pkg>` moves an existing deployment to another published version of its package (newest by default, or `--version <version>`) and keeps the values already set on it. Both forms work from a CI/CD pipeline signed in as an external app. With a key, the deployment's name, package and feed are read from the server, so no `--package-name` or `--personal-workspace` is needed, and the result also carries `FromVersion` and `InstallDeploymentKey` — the key that stays the same across upgrades, so store that one rather than `DeploymentKey`, which changes with every upgrade. It uses the same Pipelines install, so it validates before it installs: on success it reports `Status: "DeploymentSucceeded"`, `Operation`, `DeploymentStatus`, `Actions`, `ToVersion`, `PipelineDeploymentId` and `DeploymentKey`; on a validation failure it reports the errors and the deployment stays on its current version. `--no-wait` returns `Status: "Accepted"` as soon as the install is queued. An external app can only upgrade tenant-feed deployments: the server ignores the feed header on client-credentials requests, so a Personal Workspace or folder-feed deployment is refused and needs a user session.
162
+ **Upgrading in place.** `uip solution deploy upgrade <deployment-key>` (the `Key` from `deploy list`) or `uip solution deploy upgrade --name <deployment-name> --package-name <pkg>` moves an existing deployment to another published version of its package (newest by default, or `--version <version>`) and keeps the values already set on it. Both forms work from a CI/CD pipeline signed in as an external app. With a key, the deployment's name, package and feed are read from the server, so no `--package-name` or `--personal-workspace` is needed, and the result also carries `FromVersion` and `InstallDeploymentKey` — the key that stays the same across upgrades, so store that one rather than `DeploymentKey`, which changes with every upgrade. It uses the same Pipelines install, so it validates before it installs: on success it reports `Status: "DeploymentSucceeded"`, `Operation`, `DeploymentStatus`, `Actions`, `ToVersion`, `PipelineDeploymentId` and `DeploymentKey`; on a validation failure it reports the errors and the deployment stays on its current version. `--no-wait` returns `Status: "Accepted"` as soon as the install is queued. An external app can upgrade a folder-feed or Personal Workspace deployment by key only on a server that applies the feed to client-credentials requests (the same one-time check as `deploy run --feed`); on an older server it is refused and needs a user session. Tenant-feed deployments work everywhere.
163
163
 
164
164
  **Key or name — how the two forms differ.** The key form makes one extra Pipelines call, the deployment lookup, and needs nothing else: it works on any server that has that lookup. On a server without it, a user session reads the key through the Solutions API instead (tenant feed, or your Personal Workspace with `--personal-workspace`; a folder-feed deployment needs the name form) and the result carries no `FromVersion`; an external app gets `ErrorCode: not_found`, and the message points at the name form. The name form needs `--package-name` because the install route is addressed by name and nothing name-keyed in Pipelines reports a deployment's package; with `--version` as well it makes no version lookup. It does check the name exists first (the same route would otherwise treat an unknown name as a fresh install and create a deployment), so a typo fails with `ErrorCode: not_found` instead of deploying. A name whose deployment was *uninstalled* is caught the same way — the CLI checks the deployment search, which an external app can read only on servers that serve the Pipelines search — so from CI/CD on an older server address such a deployment by key, which reads its status. Find the key, the name and the package with `uip solution deploy list`.
165
165
 
@@ -203,7 +203,7 @@ So a full clean-up of a live deployment is two commands: `uninstall` removes its
203
203
 
204
204
  `uninstall` waits out an operation that blocks it: when Orchestrator refuses because the deployment still has something running, the CLI polls until that finishes and then sends the request again, all inside `--timeout` (which covers the whole command, the status poll included). If it is still busy when the timeout expires you get exit `2` with `ErrorCode: timeout` and `Retry: RetryLater` — retry later, do not treat it as permanent. A refusal for any other reason (superseded, inactive, unknown name) still fails immediately with exit `1`.
205
205
 
206
- `uninstall` and `activate` do not need a feed flag: without one they find the deployment themselves — tenant feed first, then your Personal Workspace, then the folder feeds you can reach — and scope their requests to whatever feed holds it. So the `deploy activate <name>` that `--skip-activate` points you at works the same on a `--personal-workspace` or `--feed` deployment as on a tenant one. The cost is a lookup per feed until the name is found, and a name that exists in no feed you can see is reported as not found rather than as a blocked uninstall. When you know the feed, pass it: `uninstall`, `activate` and `delete` take `--personal-workspace` or `--feed <name-or-key>` and then search that feed alone. The commands the CLI prints as next steps already carry the flag for the feed the deployment was found in. With either flag, an external-app (client-credentials) login is refused for any feed but the tenant's, because the server ignores the feed header for it.
206
+ `uninstall` and `activate` do not need a feed flag: without one they find the deployment themselves — tenant feed first, then your Personal Workspace, then the folder feeds you can reach — and scope their requests to whatever feed holds it. So the `deploy activate <name>` that `--skip-activate` points you at works the same on a `--personal-workspace` or `--feed` deployment as on a tenant one. The cost is a lookup per feed until the name is found, and a name that exists in no feed you can see is reported as not found rather than as a blocked uninstall. When you know the feed, pass it: `uninstall`, `activate` and `delete` take `--personal-workspace` or `--feed <name-or-key>` (a `Name` or `Key` from `uip solution feeds list`) and then search that feed alone. The commands the CLI prints as next steps already carry the flag for the feed the deployment was found in. With `--feed` naming a folder feed, an external-app (client-credentials) login works only on a server that applies the feed to client-credentials requests, and is refused on an older one; `--personal-workspace` is always refused to an external app.
207
207
 
208
208
  `deploy delete` and `deploy status <name>` (without a feed flag) find a name the same way. All four say "not found" only when every feed answered — with one exception: under an external-app login, `deploy status <guid>` for a GUID that is no deployment key still says "not found" when only the feeds after the tenant could not be searched, or when the tenant search refused the login (401/403), because an app login cannot read those feeds at all. When a feed cannot be searched — the feed service is down or refuses the session, the list of feeds cannot be read or gives a feed no key, or the tenant search itself fails — and no other feed has the name, they fail with a message that names the feeds they could not search instead of calling the name unknown. `ErrorCode` then comes from that failure (`server_error`, `network_error`, `authentication_required`, `permission_denied`, …, or `unknown_error` when it has no known class) and is never `not_found`; `Retry` follows it — `RetryLater` for an outage, `RetryWillNotFix` for a 401 or 403, and also `RetryWillNotFix` when every feed that could not be searched is one the list gives no key, since a retry gets the same list. Do not treat the name as wrong: do what `Instructions` say (log in again, fix the session's access, or retry later). To check one feed yourself, pass `--personal-workspace` or `--feed <name-or-key>` to `deploy status` or `deploy list`, or to the `activate`, `uninstall` or `delete` you meant to run — but `--feed` is resolved through the same list of feeds, so when that list is what failed only `--personal-workspace` helps, and `--feed` cannot pick a feed the list gives no key. When the tenant feed refuses an `activate` or `uninstall` for its own reason (401, 403, 409, 422, 429, a 5xx), that failure is reported as it is.
209
209
 
@@ -266,19 +266,7 @@ When you are signed in as an external application, the tenant is not asked: Auto
266
266
 
267
267
  Note what this means for CI: a pack that could not reach AutomationOps still returns `Result: Success` and exit `0`, so a stage using `--governance-product` as a governance gate goes green while having enforced the shipped defaults. The warning in the log is what tells you which happened — `uip solution pack` reports on governance, it does not enforce it. That warning is a `warn`-level log line. It shows on stderr at the default `--log-level`, which is `warn`; `--log-level error` hides it. A stage that needs to know reads stderr, or passes `--log-file <path>` to read it from a file. Do not combine `--log-file` with `--log-level error`: the level filter runs before a line is sent to the file, so the warning is dropped. Strict, fail-closed behaviour belongs to design-time hosts, not to this command.
268
268
 
269
- ## Dependency Feeds
270
-
271
- Packing an RPA project restores its NuGet dependencies first, so `pack` and `restore` both need to know which feeds to resolve against. So does `cleanup`: deciding that a dependency is *unused* means resolving the dependency graph, so it reads the same feeds.
272
-
273
- ```bash
274
- uip solution pack . ./out --feed-folder Shared/Production # resolve from one folder's library feed
275
- uip solution pack . ./out --nuget-sources-config-path ./NuGet.config
276
- ```
277
-
278
- By default dependencies resolve against every tenant feed the session can see.
279
-
280
- - `--feed-folder <name>` narrows that to a single Orchestrator folder's library feed — a folder name or a fully qualified path. Accepted by `pack`, `restore` and `cleanup`. It fails closed: naming a folder with no authenticated session is an error, not a silent fall back to other sources.
281
- - `--nuget-sources-config-path <path>` points at your own `NuGet.config`. Accepted by `pack` and `restore` only — `cleanup` does not take it, so a solution that packs against custom sources may clean up against different ones.
269
+ ## Package Identity and Publishing
282
270
 
283
271
  `pack` also takes `-n, --name <name>` to override the package name (it defaults to the solution folder or `.uis` file name) and `-v, --version <version>` (defaults to `1.0.0`).
284
272
 
@@ -286,23 +274,27 @@ By default dependencies resolve against every tenant feed the session can see.
286
274
 
287
275
  `--author` and `--description` apply to every member that declares neither. A project that declares its own `Description` / `Author` in its project file keeps them, so per-project provenance survives a solution pack; only when nothing declares either do the `UiPath` / `Created by UiPath` defaults apply.
288
276
 
289
- `publish` goes to the tenant feed by default:
277
+ `publish` goes to the tenant feed by default. A feed is where a package is published and deployed from: the tenant feed, your Personal Workspace, or a folder feed. `uip solution feeds list` prints each feed you can use, with its `Name`, `Key` and `Type`; every `--feed <name-or-key>` in this file takes that `Name` or `Key`.
290
278
 
291
279
  ```bash
280
+ uip solution feeds list # the feeds you can publish to and deploy from
292
281
  uip solution publish ./out/<package>.zip --personal-workspace # publish to your Personal Workspace instead
282
+ uip solution publish ./out/<package>.zip --feed <name-or-key> # publish to that feed instead
293
283
  uip solution publish ./out/<package>.zip --wait # block until the package is Ready or Active
294
284
  ```
295
285
 
296
- `publish` also accepts `--package-name` / `--package-version`, but those rewrite `solutionMetadata.json` inside the `.zip`, so they only work on a package produced by `uip solution pack`. Prefer packing with the name and version you want.
286
+ `--feed` and `--personal-workspace` cannot be combined. Deploy a package from the feed it was published to: `deploy run` takes the same `--feed <name-or-key>` or `--personal-workspace`.
297
287
 
298
- Published packages live on the tenant feed:
288
+ `publish` also accepts `--package-name` / `--package-version`, but those rewrite `solutionMetadata.json` inside the `.zip`, so they only work on a package produced by `uip solution pack`. Prefer packing with the name and version you want.
299
289
 
300
290
  ```bash
301
- uip solution packages list --limit 100 # what's published
302
- uip solution packages download <package-name> [package-version] # pull a .zip back (latest if version omitted; -d for the destination)
291
+ uip solution packages list --limit 100 # what's published to the tenant feed
292
+ uip solution packages download <package-name> [package-version] # pull a .zip back from the tenant feed (latest if version omitted; -d for the destination)
303
293
  uip solution packages delete <package-name> <package-version> --yes # remove a version (--yes required)
304
294
  ```
305
295
 
296
+ `packages list` and `packages delete` take `--feed <name-or-key>` or `--personal-workspace` to read or delete in another feed. `packages download` reads the tenant feed only.
297
+
306
298
  ## Solution Cleanup
307
299
 
308
300
  `uip solution cleanup` removes unused items from every project in the solution. For a solution directory it **modifies the project sources in place**, so check what it would do first:
@@ -315,7 +307,7 @@ uip solution cleanup . --skip-imports # apply, but leave now-unused references
315
307
 
316
308
  There is **no confirmation prompt and no `--yes` flag** — unlike `deploy uninstall` and `packages delete`, which both refuse to run without `--yes`. The bare command mutates the working tree, so run `--dry-run` first and have the tree committed.
317
309
 
318
- Cleanup decides what is unused by resolving dependencies, and it always consults whatever NuGet sources the user and machine config already define — there is no flag to turn that off. A source configured outside the solution can therefore influence what gets deleted from the project tree.
310
+ Cleanup decides what is unused by resolving dependencies, so the feeds it resolves against decide what gets deleted from the project tree. It takes the same `--feed-folder`, `--nuget-sources-config-path` and `--exclude-configured-sources` as `pack` (see "Dependency Feeds"). Clean up against the feeds you pack against: pass `--exclude-configured-sources` to drop the WorkflowCompiler's built-in feeds, so only the feeds you name take part.
319
311
 
320
312
  ## Studio Web (Browser Editing)
321
313
 
@@ -341,6 +333,8 @@ The bundle `upload` sends leaves out `.venv`, `node_modules`, `__pycache__`, `.g
341
333
 
342
334
  If Studio Web refuses the upload with 401 or 403, do **not** re-run `uip login` — the CLI checks the session and its token expiry before it calls, so the token was valid and re-authenticating produces the same one. The failure is about what the acting identity may do in Studio Web (for a CI pipeline: the external application's `StudioWebS2S` grants) or about the tenant the bundled `SolutionId` belongs to. The envelope's `Instructions` name both, and an application 401 is reported as `ErrorCode: permission_denied` rather than `authentication_required`.
343
335
 
336
+ If `solution upload` or `solution delete` fails while checking the session, it reports the actual auth failure before contacting Studio Web. `Result: ConfigError` with `ErrorCode: configuration_error` means an environment auth setting is invalid or missing; fix the setting named in `Message`. A missing session asks for `uip login`, while a session without the required organization or tenant asks you to select an active tenant with `uip login tenant set <tenant>`.
337
+
344
338
  `download` writes the `.uis` archive and nothing else — extraction is opt-in. Pass `--extract` to also unzip it into a sibling directory named after the archive; that directory is a working solution tree, with the `.uipx` manifest at its root. `--extract` also drops `AGENTS.md` and `CLAUDE.md` there so an agent picking the solution up has the same briefing `uip solution init` writes. It only fills gaps: a file the archive already carried is left alone, and the paths actually written come back in `Data.BriefingFiles`. Without `--extract` you get the zip only, and no briefing files — there is no solution directory to put them in.
345
339
 
346
340
  Two more verbs act on a **cloud** solution project rather than the local tree — do not confuse them with the local `projects add` / `import` / `remove` / `list` membership commands above:
@@ -357,7 +351,7 @@ uip solution projects resync <cloud-project-name>
357
351
  uip solution projects resync <cloud-project-name> --sync-option Reset
358
352
  ```
359
353
 
360
- `projects publish` requires all three of `--project-name`, `--package-name` and `--package-version`, and optionally takes `--folder-name`, `--description` and `--release-notes`. `projects resync` accepts the project name positionally or as `--project-name`, and `--sync-option` is `Sync` (default) or `Reset`. Both wait for the operation to finish.
354
+ `projects publish` requires all three of `--project-name`, `--package-name` and `--package-version`, and optionally takes `--folder-name`, `--description` and `--release-notes`. `projects resync` accepts the project name positionally or as `--project-name`, and `--sync-option` is `Sync` (default) or `Reset`. Both wait for the operation to finish, up to `--timeout <seconds>` (default 360). Running out exits `2` with `ErrorCode: timeout` and `Retry: RetryLater`: the operation may still be running, so check it before you run the command again. A wait that stops because the status reads keep failing exits `1` with the `ErrorCode` of that failure.
361
355
 
362
356
  ## Per-Project Bindings (`bindings_v2.json`)
363
357
 
@@ -383,7 +377,7 @@ It also generates or regenerates each project's own resources (its `package` and
383
377
 
384
378
  **Refresh is import-only for cloud resources. It never overwrites an imported resource** — that is what keeps your local edits (a renamed resource, a patched retry count) from being wiped on every re-scan. So if you change an entity, queue or asset **in the cloud** after importing it, `refresh` will not pick the change up: it reports the resource under `Skipped` and leaves it alone. To pull the new cloud definition, use `resources edit --source remote` (below).
385
379
 
386
- **A failed Resource Catalog call is not a "not found".** `resources refresh`, `pack`, `upload`, `projects add` and `projects import` look each binding up in the Resource Catalog. When that lookup fails — the catalog refuses the login with 401/403, it is unreachable, or (for `pack`, which runs without a login) there is no login — nothing is created for the binding, because a local stub would deploy as a new, empty resource instead of the one in the cloud. The same goes for a resource the catalog found but whose import was refused. A binding the solution already holds keeps that resource as it is. Refresh reports what it could not check in `Data.Warnings` and exits `0`; `projects add` / `import` log it as a warning. `pack` and `upload` fail when a binding the solution does **not** hold could not be resolved: `ErrorCode: permission_denied` for a refused login (`Retry: RetryWillNotFix`), `server_error` or `rate_limited` (`Retry: RetryLater`) when the catalog is down or throttling, and — `pack` only — `authentication_required` with no login. `resources refresh` and `upload` check the login before they start, so with no login they fail on that check instead, as before. After no login or a 401/403 the rest of the bindings are not looked up. From CI/CD, run `uip solution resources refresh` under a login the catalog accepts (a user login), commit the solution's resources, and the pipeline's `pack` then uses them as they are. An import that fails for any other reason still falls back to a local resource, and says so in the warnings.
380
+ **A failed Resource Catalog call is not a "not found".** `resources refresh`, `pack`, `upload`, `projects add` and `projects import` look each binding up in the Resource Catalog. When that lookup fails — the catalog refuses the login with 401/403, it is unreachable, or (for `pack`, which runs without a login) there is no login — nothing is created for the binding, because a local stub would deploy as a new, empty resource instead of the one in the cloud. The same goes for a resource the catalog found but whose import was refused. A binding the solution already holds keeps that resource as it is. Refresh reports what it could not check in `Data.Warnings` and exits `0`; `projects add` / `import` log it as a warning. `pack` and `upload` fail when a binding the solution does **not** hold could not be resolved: `ErrorCode: permission_denied` for a refused login (`Retry: RetryWillNotFix`), `server_error` or `rate_limited` (`Retry: RetryLater`) when the catalog is down or throttling, and — `pack` only — `authentication_required` with no login. `resources refresh` and `upload` check the login before they start, so with no login they fail on that check instead, as before. After no login or a 401/403 the rest of the bindings are not looked up. A resource the solution provisions itself from a project's own files — a case role — is never looked up, so a solution whose only unresolved bindings are case roles packs with no login. From CI/CD, run `uip solution resources refresh` under a login the catalog accepts (a user login), commit the solution's resources, and the pipeline's `pack` then uses them as they are. An import that fails for any other reason still falls back to a local resource, and says so in the warnings.
387
381
 
388
382
  `pack` and `upload` also stop if a project's contributed bindings are invalid. Fix the project's source file or inline agent and retry; these commands do not ship a solution with missing resources.
389
383
 
@@ -586,7 +580,8 @@ uip solution deploy config get <package-name> --destination config.json
586
580
  uip solution deploy config set config.json <resource-name> <property> <value>
587
581
  # e.g. set config.json MyQueue maxNumberOfRetries 5
588
582
 
589
- # Set a property on every resource (limited; supports e.g. conflictFixingAction)
583
+ # Set conflictFixingAction on every resource. --all takes only conflictFixingAction
584
+ # (exact casing); any other property is refused — set it per resource as above.
590
585
  uip solution deploy config set config.json --all <property> <value>
591
586
 
592
587
  # Link a resource slot to an existing Orchestrator resource (instead of creating a new one)
@@ -634,7 +629,7 @@ Three rules make automation reliable:
634
629
  A filter that selects nothing still returns `Result: "Success"` with `Data: []` and exit 0 — that is a valid empty answer, not a failure. Check the `Warning` field and stderr. They say which it was: a field name that does not exist (fix the expression), no record matched or the expression resolved to no value (the answer really is empty), or a name that reads below the top level (`Items[].Name` reads `Name` off an `Items` entry, so only `Items` was checked — an empty `Items` is the usual cause, not a bad name).
635
630
 
636
631
  Standard success shape: `{ "Result": "Success", "Code": "<CommandCode>", "Data": ... }`.
637
- Standard failure shape: `{ "Result": "Failure", "Message": "<short>", "Instructions": "<actionable>" }`.
632
+ Standard failure shape: `{ "Result": "Failure", "ErrorCode": "<code>", "Message": "<short>", "Instructions": "<actionable>", "Retry": "<hint>" }`. Every failure carries `ErrorCode` and `Retry`, so branch on them rather than on `Message`. `Result` is not always `Failure`: an option or argument the CLI rejects before running gives `ValidationError`, for example. `ErrorCode` is a fixed set (`invalid_argument`, `authentication_required`, `permission_denied`, `not_found`, `timeout`, `network_error`, `server_error`, `unknown_error`, …). `Retry` says whether running the same command again can help: `RetryWillNotFix` means change the input, login or access first; `RetryLater` and `RetryAfter<N>Seconds` mean the failure may clear on its own.
638
633
 
639
634
  List commands always return `Data: []` on empty results — never a message object — so consumers can rely on a consistent array shape.
640
635
 
@@ -674,11 +669,14 @@ Adjacent groups commonly used alongside solutions:
674
669
  | Symptom | First thing to check |
675
670
  |---|---|
676
671
  | `Not authenticated` / 401 | `uip login`, then re-run |
672
+ | `pack` fails with `Context.ErrorCode: case_role_unbound` | A Case project's `metadata.caseRoles` declares a role that has no `Role` entry in its `bindings_v2.json`, so the pack would deploy without it. Run `uip maestro case bindings sync <plan>` in that project (the message names the plan file and the directory), then pack again. The sync writes one `Role` entry per role; pack mints the role resource from it and writes the role's permissions onto that resource, as Studio Web's publish writes them (a retired `CaseManagement.Cases.Manage` and, on a stage role, a permission a stage cannot grant are left out) |
673
+ | `pack` fails with `Context.ErrorCode: case_role_name_collision` | One Case project declares two roles whose names differ only by letter case. The schema keeps them apart, but the solution stores one role resource per name regardless of case, so they would deploy as one. Rename one of them in the Case Designer, run `uip maestro case bindings sync <plan>` in that project, then pack again |
674
+ | `pack` fails with `Context.ErrorCode: contribution_conflict` (`Projects '…', '…' each contribute a 'role' named '…' with different actions`) | Two Case projects in the solution declare a case role of the same name with different permissions. A role is one resource for the whole solution, so the pack refuses rather than pick one. Give both plans the same permissions for that role, or rename one of them, then run `uip maestro case bindings sync <plan>` in the project you changed and pack again |
677
675
  | `upload` fails with 401/403 and `ErrorCode: permission_denied` | Not a login problem — the token was valid when the call went out, so `uip login` mints the same one. Read `Instructions`: for a session on an external application, check that the app has the Studio Web (`StudioWebS2S`) grants, not only the Orchestrator and Solutions ones; for a user, check Studio Web access in the tenant. Then confirm the `SolutionId` in the `.uipx` belongs to the tenant you are logged into — one from another tenant is refused, not reported missing |
678
- | `packages list` or `deploy list` fails with `ErrorCode: permission_denied` from a CI/CD pipeline | Both accept an external app on servers that serve their Pipelines search (`POST /v1/pipelines/packages/search`, `POST /v1/pipelines/deployments/search`). An app is refused only on an older server, which has just the user-only search (the message says so), or with `--personal-workspace` or a folder `--feed`, whose feed the server ignores for an app (a `--feed` naming the tenant feed works). A `--feed` is checked against the Studio Web publish locations, so an app needs a `StudioWebS2S` grant for it; the message names it when that lookup is refused. `uip login` with the same app mints the same kind of token; run the listing under a user session, or drop the feed flag to list the tenant feed. The same goes for `--personal-workspace` on any command: an external app has no Personal Workspace. |
676
+ | `packages list` or `deploy list` fails with `ErrorCode: permission_denied` from a CI/CD pipeline | Both accept an external app on servers that serve their Pipelines search (`POST /v1/pipelines/packages/search`, `POST /v1/pipelines/deployments/search`). An app is refused only on an older server, which has just the user-only search (the message says so), or with `--personal-workspace`, or with a folder `--feed` on a server that does not yet apply the feed to an app's requests (a `--feed` naming the tenant feed works). A `--feed` name is checked against the Studio Web publish locations, which an app reads only with a `StudioWebS2S` grant; without it the CLI uses a `--feed` folder key as given and looks a folder path up through Orchestrator (`OR.Folders`), and the message names those options when that fails too. `uip login` with the same app mints the same kind of token; run the listing under a user session, or drop the feed flag to list the tenant feed. The same goes for `--personal-workspace` on any command: an external app has no Personal Workspace. |
679
677
  | `pack` or `upload` fails with `ErrorCode: permission_denied` (or `pack` with `authentication_required`) and a message naming the Resource Catalog | The catalog refused the login (or there was none), so bindings the solution does not hold yet could not be resolved, and the command will not pack them as empty stubs. Run `uip solution resources refresh` under a user login, commit the solution's resources, then re-run. Bindings already in the solution are fine as they are |
680
678
  | Command targets the wrong tenant | `uip login tenant set <tenant>`; verify with `uip login status` |
681
- | Pack succeeds but publish 409s | Version conflict — bump the version (`uip solution pack . ./out -v <new-version>`) or delete the colliding version with `uip solution packages delete <package-name> <version> --yes` (only if intentional; `--yes` required) |
679
+ | Pack succeeds but publish 409s | Version conflict — bump the version (`uip solution pack . ./out -v <new-version>`) and publish that. Do not delete the published version to reuse its number: anything deployed from it depends on it. Delete it only when the user asks for it — `uip solution packages delete <package-name> <version> --yes`. The CLI never prompts, so `--yes` is the only check; ask the user first |
682
680
  | `deploy run` stops because the package is already deployed | Upgrade it in place with `uip solution deploy upgrade <deployment-key>` (running `deploy run` again does not upgrade it), or `uip solution deploy uninstall <name> --yes` then `uip solution deploy delete <name> --yes` first, or pass `--yes` with a different `--name` to create a second, separate deployment (re-using the name updates the existing one in place) |
683
681
  | `HTTP 400 … cannot be uninstalled` (error `4007`) | The deployment is not uninstallable in its state — superseded, already uninstalled, or left by a failed install. Read `Instructions`: when its `Actions` list offers `Delete`, remove the record with `uip solution deploy delete <name> --yes`. An operation still running is the other cause, and that one clears by itself (`Retry: RetryLater`) |
684
682
  | `deploy uninstall` fails with `Message` "Uninstall failed with status: FailedUninstall: this deployment has uncompleted jobs…" or "…permanently deletes these resources and their data: …", or "Deployment '<name>' was not uninstalled: …" | Orchestrator wants explicit consent: the deployment has uncompleted jobs (`Data.JobsNotInFinalState: true`), or uninstalling it permanently deletes resources that were replaced by links (`Data.PermanentDeletionResources`; the "was not uninstalled" form is the synchronous HTTP 409, error `4026`). Re-run with `--force` only if that is acceptable; otherwise let the jobs finish first. Retrying without `--force` does not help (`Retry: RetryWillNotFix`) |
package/dist/tool.js CHANGED
@@ -1,37 +1,36 @@
1
1
  import {
2
- metadata,
3
- registerCommands
4
- } from "./packager-tool-cjjk2ek2.js";
5
- import"./packager-tool-kkfb5kgn.js";
6
- import"./packager-tool-amhyxzz6.js";
7
- import"./packager-tool-gmwva4yv.js";
8
- import"./packager-tool-d3cmmbw1.js";
9
- import"./packager-tool-r1jvvm8y.js";
10
- import"./packager-tool-d8ng7mex.js";
11
- import"./packager-tool-3gwrcgrc.js";
12
- import"./packager-tool-ph7fg1aa.js";
13
- import"./packager-tool-a4bs7wtm.js";
14
- import"./packager-tool-act5r386.js";
15
- import"./packager-tool-mq5pc4zr.js";
16
- import"./packager-tool-3bwnkjdq.js";
17
- import"./packager-tool-gs3f3tf7.js";
18
- import"./packager-tool-4pkzxkty.js";
19
- import"./packager-tool-rg3xgn9a.js";
20
- import"./packager-tool-97rcgwvv.js";
21
- import"./packager-tool-sxjehksx.js";
22
- import"./packager-tool-qw47eyw7.js";
23
- import"./packager-tool-61pwb567.js";
24
- import"./packager-tool-8ptbmmmp.js";
25
- import"./packager-tool-5edvzz80.js";
26
- import"./packager-tool-43ahv5mn.js";
27
- import"./packager-tool-tx834spe.js";
28
- import"./packager-tool-6ybywxxn.js";
29
- import"./packager-tool-v1f5e8t9.js";
30
- import"./packager-tool-dfrk01gn.js";
31
- import"./packager-tool-1de529jm.js";
2
+ metadata2,
3
+ registerCommands2
4
+ } from "./packager-tool-t3ahzjh1.js";
5
+ import"./packager-tool-vrqbbh01.js";
6
+ import"./packager-tool-x33sdw6n.js";
7
+ import"./packager-tool-vx2c68sb.js";
8
+ import"./packager-tool-1bz9h5ca.js";
9
+ import"./packager-tool-55ztfccd.js";
10
+ import"./packager-tool-q8ryk6q9.js";
11
+ import"./packager-tool-snm6s7b5.js";
12
+ import"./packager-tool-q5d9df2q.js";
13
+ import"./packager-tool-wm0h0wa1.js";
14
+ import"./packager-tool-w8bcwfd3.js";
15
+ import"./packager-tool-fx4ws49n.js";
16
+ import"./packager-tool-1ctvbx0h.js";
17
+ import"./packager-tool-vx39dhvn.js";
18
+ import"./packager-tool-fqs6hdcy.js";
19
+ import"./packager-tool-vrtabg73.js";
20
+ import"./packager-tool-bs1jn1yn.js";
21
+ import"./packager-tool-a6va4gc5.js";
22
+ import"./packager-tool-f84z7nds.js";
23
+ import"./packager-tool-fp46ebde.js";
24
+ import"./packager-tool-ppj5f4y7.js";
25
+ import"./packager-tool-c64hqa8n.js";
26
+ import"./packager-tool-t39pjz7n.js";
27
+ import"./packager-tool-9vrwpgt3.js";
28
+ import"./packager-tool-m07vyk89.js";
29
+ import"./packager-tool-vgrswa8p.js";
30
+ import"./packager-tool-rj2d1g0w.js";
32
31
  export {
33
- metadata,
34
- registerCommands
32
+ metadata2 as metadata,
33
+ registerCommands2 as registerCommands
35
34
  };
36
35
 
37
- //# debugId=B0CD5F2BE1565ADD64756E2164756E21
36
+ //# debugId=A132CD581B16DFE164756E2164756E21
package/package.json CHANGED
@@ -2,7 +2,7 @@
2
2
  "name": "@uipath/solution-tool",
3
3
  "author": "UiPath",
4
4
  "license": "SEE LICENSE IN LICENSE.txt",
5
- "version": "1.205.0-preview.277",
5
+ "version": "1.206.0-preview.279",
6
6
  "description": "Create, pack, publish, and deploy UiPath Automation Solutions.",
7
7
  "repository": {
8
8
  "type": "git",
@@ -48,5 +48,5 @@
48
48
  "dist"
49
49
  ],
50
50
  "private": false,
51
- "gitHead": "0dc7b5ef3ba1d723a8f2eee6b760c20f4ac294c7"
51
+ "gitHead": "d2176feff38d4e91a9d84723af847b2dfd5c6008"
52
52
  }
@@ -1,25 +0,0 @@
1
- import {
2
- deleteDeploymentAsync
3
- } from "./packager-tool-wrg41m7t.js";
4
- import"./packager-tool-d8ng7mex.js";
5
- import"./packager-tool-3gwrcgrc.js";
6
- import"./packager-tool-act5r386.js";
7
- import"./packager-tool-mq5pc4zr.js";
8
- import"./packager-tool-rg3xgn9a.js";
9
- import"./packager-tool-97rcgwvv.js";
10
- import"./packager-tool-sxjehksx.js";
11
- import"./packager-tool-qw47eyw7.js";
12
- import"./packager-tool-61pwb567.js";
13
- import"./packager-tool-8ptbmmmp.js";
14
- import"./packager-tool-5edvzz80.js";
15
- import"./packager-tool-43ahv5mn.js";
16
- import"./packager-tool-tx834spe.js";
17
- import"./packager-tool-6ybywxxn.js";
18
- import"./packager-tool-v1f5e8t9.js";
19
- import"./packager-tool-dfrk01gn.js";
20
- import"./packager-tool-1de529jm.js";
21
- export {
22
- deleteDeploymentAsync
23
- };
24
-
25
- //# debugId=75D578D2E0DE171A64756E2164756E21
@@ -1,25 +0,0 @@
1
- import {
2
- deployRunAsync
3
- } from "./packager-tool-hsya909c.js";
4
- import"./packager-tool-ph7fg1aa.js";
5
- import"./packager-tool-a4bs7wtm.js";
6
- import"./packager-tool-act5r386.js";
7
- import"./packager-tool-mq5pc4zr.js";
8
- import"./packager-tool-rg3xgn9a.js";
9
- import"./packager-tool-97rcgwvv.js";
10
- import"./packager-tool-sxjehksx.js";
11
- import"./packager-tool-qw47eyw7.js";
12
- import"./packager-tool-61pwb567.js";
13
- import"./packager-tool-8ptbmmmp.js";
14
- import"./packager-tool-5edvzz80.js";
15
- import"./packager-tool-43ahv5mn.js";
16
- import"./packager-tool-tx834spe.js";
17
- import"./packager-tool-6ybywxxn.js";
18
- import"./packager-tool-v1f5e8t9.js";
19
- import"./packager-tool-dfrk01gn.js";
20
- import"./packager-tool-1de529jm.js";
21
- export {
22
- deployRunAsync
23
- };
24
-
25
- //# debugId=D1942F34DAF6583664756E2164756E21