🚨 Breaking Changes for UiPath Python SDK (v2.2.0+)

Release Date: November 26, 2025

Version 2.2.0 of the UiPath Python SDK introduces exciting new features alongside several breaking changes affecting both the SDK and CLI.

What's New

1. Studio Web Integration

uipath push / uipath pull - Upload your Python scripts and agents to Studio Web and add them to solutions for team collaboration and deployment.

2. Evaluation Framework

uipath eval - Run evaluations on your agents and workflows to measure performance, accuracy, and reliability.

3. Developer Console

uipath dev - Launch the UiPath Developer Console for an enhanced development experience with debugging and monitoring capabilities.

Breaking Changes

1. Minimum Python Version: 3.11+ Required

What's changing: Python 3.10 is no longer supported for uipath-python, uipath-langchain-python, uipath-llamaindex-python.

Action required: Upgrade to Python 3.11 or higher.

2. Import Path Change

What's changing: The UiPath class has moved from uipath to uipath.platform.

Action required: Update your imports:

# Before
from uipath import UiPath
from uipath.models import Job, Asset, Queue
from uipath.models import Entity 
from uipath.models import CreateAction, WaitAction, WaitJob, InvokeProcess

# After
from uipath.platform import UiPath
from uipath.platform.orchestrator import Job, Asset, Queue
from uipath.platform.entities import Entity
from uipath.platform.common import CreateTask, WaitTask, WaitJob, InvokeProcess

client = UiPath(...)

3. Transition to LangChain v1 (for uipath-langchain only)

What's changing: Minimum required versions are now LangChain 1.0.0+ and LangGraph 1.0.0+

Action required: Review and update your code according to the LangChain v1 Migration Guide.

Note: This only applies if you're using the uipath-langchain package.

4. Configuration Architecture Redesign

We've restructured how UiPath projects define and manage their resources:

uipath.json - Configuration File (Updated Purpose)

• Previously contained entrypoints and bindings; now serves as a streamlined configuration file
• For pure Python scripts, define entrypoints in the functions section:

  {
    "functions": {
      "entrypoint1": "src/main.py:main",
      "entrypoint2": "src/graph.py:run"
    }
  }

• For LangGraph graphs, define entrypoints in langgraph.json (same as before)
• For LlamaIndex workflows, define entrypoints in llamaindex.json (same as before)

bindings.json - Manual Binding Definitions (New)

• Overridable resources (bindings) now stored in a separate file
• Bindings are no longer automatically inferred from code
• Must be manually defined by the user for now (we're working on an interactive configurator to simplify this process)

entry-points.json - I/O Schema (New)

• Contains the input/output schema for your entrypoints
• Automatically inferred from code based on entrypoints defined in llamaindex.json/langgraph.json/uipath.json

You can find the complete specifications and JSON schemas for configurations files here: https://github.com/UiPath/uipath-python/tree/main/specs

5. Removed azure-monitor-opentelemetry dependency

What's changing: The azure-monitor-opentelemetry dependency has been removed from the SDK: #904

Why: This dependency was causing the CLI to hang in certain scenarios.

Action required: If your code relies on packages that were previously installed as transitive dependencies of azure-monitor-opentelemetry (such as requests), you'll need to explicitly add them to your pyproject.toml:

dependencies = [
    "uipath>=2.2.0,<2.3.0",
    "requests",  # Add if you use requests directly
    # Add any other previously transitive dependencies you need
]

Note: If you were using Azure Monitor for observability, you'll need to install and configure it separately in your project.

Migration Guide

Stay on v2.1.x

To avoid these breaking changes and keep your current setup, pin your dependency in pyproject.toml:

"uipath>=2.1.x,<2.2.0"

For uipath-langchain users: To stay on the current version without LangChain v1:

"uipath-langchain>=0.0.x,<0.1.0"

Migrate to v2.2.0+

1. Upgrade to v2.2.0+

   Update the dependencies in pyproject.toml with:

   "uipath>=2.2.x,<2.3.0"

For uipath-langchain users:
To migrate to LangChain v1:

   "uipath-langchain>=0.1.0,<0.2.0"

For uipath-langchain/uipath-llamaindex users:
Make sure to also reference uipath in your pyproject.toml - future versions will no longer reference the main uipath CLI package as a dependency.

1. Upgrade the Python version to 3.11+

   In pyproject.toml specify the required Python version by adding or updating the following field:

   requires-python = ">=3.11"

1. Update imports

   Change from uipath import UiPath to from uipath.platform import UiPath.

2. Review LangChain v1 changes (if using uipath-langchain)

   Review the LangChain v1 Migration Guide and update your code accordingly.

3. Update configuration files

   • Define your entrypoints in functions within uipath.json (not applicable if you already use langgraph.json/llamaindex.json)
   • Run uipath init to automatically generate the entry-points.json I/O schema from your configuration
   • Create bindings.json and manually define all overridable resources
   • Important: If you update your script/agent code, run uipath init again to regenerate the I/O schema

For questions or issues, please open a ticket: UiPath Python SDK Submit Issue