25.10.3

Release date: 24 November 2025

What's new

• Installing UiPath CLI via .NET tool
• Signing Packages
• New macOS Platform Support Added
• Support default application scopes for all commands
• Test Manager Support
• Automatically filled process description from package description
• Add author parameter for pack and test commands

Installing UiPath CLI via .NET tool

UiPath CLI 25.10 can now be installed as a .NET global tool, providing a streamlined installation experience across all platforms. This method automatically handles dependencies and makes the CLI available system-wide.

The UiPath CLI packages are published to NuGet.org, the public .NET package feed, making installation straightforward using the dotnet tool install command.

Prerequisites:

• .NET 8 SDK installed on your system

Install the latest version:

# Windowsdotnet tool install --global UiPath.CLI.Windows# Linuxdotnet tool install --global UiPath.CLI.Linux# macOS (ARM64 only)dotnet tool install --global UiPath.CLI.macOS

Note:

UiPath.CLI.Windows.Legacy is not available as a .NET tool. It must be downloaded manually from the UiPath public feed and extracted to your system or using Azure Devops or Jenkins plugins to install UiPath CLI.

Install a specific version:

# Install version 25.10.3dotnet tool install --global UiPath.CLI.Windows --version 25.10.3# Install version 25.10.3dotnet tool install --global UiPath.CLI.macOS --version 25.10.3

Update to the latest version:

dotnet tool update --global UiPath.CLI.Windows

List installed tools:

dotnet tool list --global

Uninstall:

dotnet tool uninstall --global UiPath.CLI.Windows

After installation, verify the CLI is available:

uipcli --version

Tip:

Using dotnet tool install is the recommended installation method as it simplifies version management and ensures proper .NET SDK dependencies are met.

Signing Packages

UiPath CLI 25.10 introduces the ability to digitally sign automation packages during the pack operation. Package signing provides:

Security benefits:

• Authenticity verification - Confirm the package comes from a trusted source
• Integrity protection - Detect any tampering or modifications after creation
• Non-repudiation - Cryptographically prove package origin
• Compliance - Meet regulatory requirements for software distribution

Why sign packages:

• Protect against malicious package substitution in your deployment pipeline
• Establish trust chain from development to production
• Enable security policies that only allow signed packages
• Provide audit trail for package provenance

Use cases:

• Enterprise deployments requiring verified software
• Multi-team environments where package origin must be validated
• Regulated industries with compliance requirements
• Production environments with strict security policies

For detailed implementation guide, usage examples, and best practices, see:

• Signing Project Packages
• Signing Solution Packages

New macOS Platform Support Added

UiPath CLI 25.10 introduces native support for macOS on ARM64 architecture (Apple Silicon), enabling developers to build, analyze, and package Cross-platform projects on M1, M2, and M3 Mac computers. The new UiPath.CLI.macOS package brings the full CLI capabilities to macOS environments.

Note:

macOS support is currently available for ARM64 (Apple Silicon) processors only. Intel-based Macs are not supported.

System requirements for macOS

• macOS 11 (Big Sur) or later
• Apple Silicon (M1/M2/M3) - ARM64 architecture required
• .NET 8 SDK for macOS ARM64
• Minimum 4 GB RAM recommended

Getting started on macOS

To use UiPath CLI on macOS:

1. Install .NET 8 SDK for macOS ARM64 from Microsoft's website
2. Install UiPath CLI using the .NET tool command:

dotnet tool install --global UiPath.CLI.macOS

Verify installation:

uipcli --version

Default Application Scopes

UiPath CLI 25.10 introduces default application scopes for external application authentication. When no explicit --applicationScope parameter is specified, the CLI now applies service-specific default scopes tailored for common operations, eliminating the need to manually configure extensive permission lists.

Default scope sets:

The CLI automatically applies different default scopes depending on the target service:

1. For Orchestrator operations:

   OR.Assets OR.BackgroundTasks OR.Execution OR.Folders OR.Robots.Read OR.Machines.Read OR.Jobs OR.TestSets OR.TestSetExecutions OR.Monitoring OR.Settings.Read

2. For Solution operations:

   Solutions.Packages Solutions.Deployments OR.Execution

3. For Test Manager operations:

   TM.Projects TM.TestSets TM.TestExecutions

Usage examples:

Before (manual scope specification):

uipcli package deploy "path/to/project" --applicationId "app-id" --applicationSecret "secret" --accountForApp "organization" --applicationScope "OR.Jobs.Read OR.Execution OR.Folders OR.Assets"

After (automatic service-specific defaults):

uipcli package deploy "path/to/project" --applicationId "app-id" --applicationSecret "secret" --accountForApp "organization"

Custom scope override:

For specialized scenarios requiring specific permissions, you can still explicitly specify the --applicationScope parameter to override the defaults:

uipcli package deploy "path/to/project" --applicationId "app-id" --applicationSecret "secret" --accountForApp "organization" --applicationScope "OR.Execution OR.Folders"

This feature applies to all CLI commands that support external application authentication.

Test Manager Support

UiPath CLI 25.10 introduces support for Test Manager, the next-generation testing platform for UiPath. Test Manager provides enhanced test management capabilities, better collaboration features, and improved reporting compared to the legacy Orchestrator Testing Module.

Warning:

The Orchestrator Testing Module is being phased out and replaced by Test Manager, which provides a unified testing experience, expanded capabilities, and full CI/CD integration.

Deprecation timeline (as announced by the Test Manager team):

• Cloud: Orchestrator Testing Module will be discontinued on January 1, 2026.
• Automation Suite: Testing Module will be removed April 2026 (six months after the 2.2510 feature-parity release).
• On-premises (MSI): No deprecation announced. UiPath CLI will continue to support Orchestrator testing for on-premises MSI installations.

Impact on UiPath CLI:

UiPath CLI 25.10 introduces support for Test Manager to align with this transition. The CLI will continue to support Orchestrator-based testing commands for:

• On-premises MSI installations (indefinitely, until further notice)
• Cloud and Automation Suite environments (until the deprecation dates above)

Migration recommendations:

• Cloud customers: Migrate to Test Manager before January 1, 2026.
• Automation Suite customers: Plan migration for completion by April 2026.
• On-premises MSI customers: Continue using Orchestrator-based testing with UiPath CLI.

For more information, see the official deprecation timeline.