CI/CD integrations release notes

Last updated Nov 12, 2025

25.10.1-20251105-9

Release date: 6 November 2025

What's new

Solutions support

UiPath CLI 25.10 introduces full lifecycle support for Solutions, a new packaging format that combines multiple project types and configurations into a single deployable unit.

New CLI commands:

solution restore - Restore Solution dependencies
solution analyze - Analyze Solution for governance and quality
solution pack - Pack a Solution into a distributable artifact
solution upload-package - Upload Solution package to Automation Cloud
solution delete-package - Delete Solution package from Automation Cloud
solution download-package - Download Solution package
solution download-config - Download Solution configuration file
solution deploy - Deploy Solution package to target environment
solution deploy-activate - Activate Solution deployment with environment-specific configurations
solution deploy-uninstall - Uninstall Solution deployment from environment

CLI package split The CLI distribution has been restructured for better alignment with project types:

UiPath.CLI.Windows.Legacy was introduced as a separate package for building Windows - Legacy RPA projects.
UiPath.CLI was renamed to UiPath.CLI.Linux for consistency.
All three packages now require .NET 8 Runtime.

Breaking changes

Important:

UiPath CLI 25.10 introduces significant changes to package structure and project type support. Review these breaking changes carefully.

CLI package split and flavor selection

What changed: UiPath CLI is now distributed in three separate packages:

UiPath.CLI.Windows - for Cross-platform and Windows (non-legacy) projects
UiPath.CLI.Linux - for Cross-platform projects on Linux
UiPath.CLI.Windows.Legacy - for Windows - Legacy projects only

Why this matters:

Windows - Legacy projects can no longer be packaged using UiPath.CLI.Windows.
You must use UiPath.CLI.Windows.Legacy for all Windows - Legacy projects.
The previous UiPath.CLI package has been renamed to UiPath.CLI.Linux.

Mixed project types in the same repository

What changed: If your repository contains both Windows - Legacy projects and other project types (Cross-platform or Windows non-legacy), you must:

Download and use both CLI packages:
- UiPath.CLI.Windows for Cross-platform and Windows projects
- UiPath.CLI.Windows.Legacy for Windows - Legacy projects
Structure your build/CI process to invoke the correct CLI for each project type.

Example approach:

# Process modern projectsuipcli.exe package pack "CrossPlatformProject.json" --output "./packages"# Switch to Legacy CLIuipcli-legacy.exe package pack "LegacyProject.json" --output "./packages"# Process modern projectsuipcli.exe package pack "CrossPlatformProject.json" --output "./packages"# Switch to Legacy CLIuipcli-legacy.exe package pack "LegacyProject.json" --output "./packages"

Important notes:

The CLI does not automatically detect project types.
You must identify which projects are Windows - Legacy and organize your build scripts accordingly.
Consider separating projects by type into different folders or repositories for easier management.

.NET Runtime requirement

What changed: All UiPath CLI 25.10 packages now require .NET 8 Runtime (previous versions used .NET 6).

Action required:

Install .NET Desktop Runtime 8 (Windows) or .NET Runtime 8 (Linux).
Update build agent and developer machine requirements.

Plugin integration changes

The updated Azure DevOps extension (v6.0) and Jenkins plugin (v6.0) now install only UiPath CLI 25.10 or later.
Older CLI versions (23.x or 24.x) are no longer distributed by the plugin installers.
Existing pipelines must be updated to explicitly reference one of the new CLI flavors.

For detailed migration guidance for CI/CD pipelines, refer to:

Compatibility requirements