CI/CD integrations release notes

Solutions support​

• 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​

• 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.

CLI package split and flavor selection​

What changed​

• 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​

1. Download and use both CLI packages:

   • UiPath.CLI.Windows for Cross-platform and Windows projects
   • UiPath.CLI.Windows.Legacy for Windows - Legacy projects

2. Structure your build/CI process to invoke the correct CLI for each project type.

Example approach​

# Process modern projects
dotnet uipcli.dll package pack "CrossPlatformProject.json" --output "./packages"

# Switch to Legacy CLI
uipcli-legacy.exe package pack "LegacyProject.json" --output "./packages"
# Process modern projects
dotnet uipcli.dll package pack "CrossPlatformProject.json" --output "./packages"

# Switch to Legacy CLI
uipcli-legacy.exe package pack "LegacyProject.json" --output "./packages"

• 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.

What changed​

Action required​

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

• 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.

• Jenkins Plugin v6.0 Release Notes
• Azure DevOps Extension 6.0 Release Notes

Compatibility requirements​

• Compatible with UiPath Studio 25.10+
• Compatible with UiPath Robot 25.10+
• Compatible with Orchestrator 25.10+ (Automation Cloud or Standalone)
• Solutions deployment is currently Automation Cloud only

Enhanced project support​

• Template projects are now supported.

Limitations​

• Windows - Legacy projects cannot be included in Solutions.
• Solutions are currently supported only in Automation Cloud (not Standalone Orchestrator)