25.10.16

Release date: May 18, 2026

• New --activitiesRootCategory parameter for library projects, to override the activity category prefix exposed by the published library.
• New --skipAnalyze and --skipValidate parameters for skipping Workflow Analyzer and project validation during the pack step.
• New --excludeConfiguredSources parameter to make NuGet restore ignore user-level and machine-level sources from the host running the CLI.
• Faster pack on Linux and macOS when projects produce a high volume of Workflow Analyzer warnings.
• Faster restore on projects with many dependencies — eliminated duplicate NuGet downloads within a single CLI run.
• CLI now prints its version and runtime on the first line of every invocation, so support logs always identify which build ran.

Novidades

Override the activities root category when packing a library

When you pack a library project, every activity exposed by the resulting package gets a root category prefix. By default, that prefix is the library project name. The new --activitiesRootCategory parameter lets you override it without renaming the project.

uipcli package pack "C:\projects\MyLibrary\project.json" -o "C:\Output" --activitiesRootCategory "MyCompany.Finance.Invoicing"

Activities in the resulting .nupkg will appear under MyCompany.Finance.Invoicing in the Studio Activities panel of any project that installs the library.

The parameter has effect only when packing a library project. It is ignored for Process, Tests, and Objects output types. When omitted, the behavior is unchanged: the root category falls back to the library project name, matching what the Library Publish dialog in Studio produces.

Skip analyzer and validation during pack

Workflow Analyzer and project validation run automatically as part of package pack. Two new flags let you opt out of either step:

• --skipAnalyze — skip running Workflow Analyzer during the pack step.
• --skipValidate — skip the project validation step during the pack step.

uipcli package pack "C:\projects\MyProject\project.json" -o "C:\Output" --skipAnalyze --skipValidate

Use these flags when:

• Your pipeline already runs package analyze or validates the project in an earlier stage (for example, on a pre-merge check), and you don't want to pay the same cost again on pack.
• You're producing a quick package for local debugging and only need the artifact.

For release pipelines, the recommendation is still to leave both steps enabled.

Resolve dependencies only from --nugetConfigFilePath

The new --excludeConfiguredSources flag excludes UiPath's built-in feeds and the user-level and machine-level NuGet configuration on the host running the CLI (typically %AppData%\NuGet\NuGet.Config and %ProgramFiles(x86)%\NuGet\Config). The CLI resolves packages only from the feeds defined in the nuget.config file you pass through --nugetConfigFilePath.

uipcli package pack "C:\projects\MyProject\project.json" -o "C:\Output" \
  --nugetConfigFilePath "C:\ci\nuget.config" \
  --excludeConfiguredSources

Use this flag when:

• You want hermetic, reproducible builds where only the feeds you declare in version control are consulted.
• A shared build agent has machine-level feeds that you don't want bleeding into specific pipelines.
• You're debugging "works on agent A, fails on agent B" issues caused by divergent host-level NuGet configuration.

Quando você executar uipcli com um arquivo de configuração, defina "excludeConfiguredSources": true.

Make sure your nuget.config declares every feed the project needs — including any UiPath feed equivalents — because no other source is consulted when this flag is set.

Improved performance on Linux and macOS for analyzer-heavy projects

When packing a project that produces a high volume of Workflow Analyzer warnings on Linux or macOS, the CLI previously took several minutes to drain analyzer messages after the actual compile finished. The internal communication channel between the CLI and the SolutionPackager has been switched to a named-pipe / Unix domain socket transport, removing that bottleneck.

No user action is required — packs that took 15+ minutes on Linux for verbose analyzer output now complete in seconds after the compile finishes. Windows behavior is unchanged.

Faster restore — no more duplicate NuGet downloads in a single run

When a single CLI invocation triggered multiple restore steps (for example a pack that validates and then packs, or a solution pack that restores each project), the same NuGet packages could be downloaded more than once because the HTTP cache window had already expired between steps. The CLI now keeps already-downloaded packages cached for 15 minutes within a single run, so subsequent restore steps reuse the local copies instead of re-fetching from the feed.

No user action is required — projects with many dependencies see noticeable speedup on commands that perform a NuGet restore.

Version and runtime printed at startup

Every CLI invocation now prints a banner as its first line of output:

uipcli: version 25.10.16, running on .NET 8.0.x

This makes support logs self-describing — there is no ambiguity about which CLI build or which runtime produced a given log file.

Updated documentation

• Empacotando projetos em um pacote
• Restaurando dependências de automação
• Análise de um projeto
• Teste de um pacote ou execução de um conjunto de testes
• Gerenciando feeds do NuGet