NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
PyPI, #3206 most downloaded on PyPI
Python SDK and CLI for UiPath Platform, enabling programmatic interaction with automation services, process management, and deployment tools.
Latest stable
2.15.2
Last release 12 days ago
10 Nov 2026
Ships on a steady schedule
a new release about every 1 weeks
No release notes found
nothing matched a version
15 versions withdrawn
withdrawn after publishing
8 years old
703 releases · first in 2019
Drag across the ruler to compare, or tap a release to open it.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
These are breaking changes for code that uses the affected public names. Update as follows:
The eval framework's central execution type and its keyword parameters were renamed to unified-evals terminology. The value passed to every evaluator represents a workload execution (agent, process/orchestration, case management, …), not specifically an agent.
These are breaking changes for code that uses the affected public names. Update as follows:
| Before | After |
|---|---|
from uipath.eval.models import AgentExecution |
from uipath.eval.models import WorkloadExecution |
WorkloadExecution(agent_trace=...) |
WorkloadExecution(workload_trace=...) |
WorkloadExecution(agent_output=...) |
WorkloadExecution(workload_output=...) |
execution.agent_trace / execution.agent_output |
execution.workload_trace / execution.workload_output |
evaluator.evaluate(agent_execution=...) |
evaluator.evaluate(workload_execution=...) |
evaluator.validate_and_evaluate_criteria(agent_execution=...) |
evaluator.validate_and_evaluate_criteria(workload_execution=...) |
What still works:
AgentExecution (the class name) is soft-deprecated: importing it still resolves to
WorkloadExecution and emits a DeprecationWarning (removed in uipath 3.0). Note the
fields are not aliased — constructing AgentExecution(agent_output=..., agent_trace=...)
now raises a ValidationError; rename the fields as above.evaluate / validate_and_evaluate_criteria with the old
agent_execution parameter name keep running, because the runtime dispatches positionally.
Only callers passing agent_execution= by keyword are affected.Unchanged (intentionally): the WorkloadExecution.agent_input and
expected_agent_behavior fields, and the agent_output / agent_execution_time fields on
EvalRunUpdatedEvent and StudioWebProgressItem (the latter a Studio Web wire contract).
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
This release contains no breaking changes.
uipath.json now carries a stable id (a GUID) that durably identifies the project across packaging and tracing.
uipath init generates the id on first run and backfills it into an existing uipath.json that lacks one. If the project already has an identity (a Studio Web project id, or a legacy .uipath/.telemetry.json ProjectKey), that value is reused instead of minting a new one.uipath pack uses uipath.json#id as the projectId in operate.json, falling back to the legacy sources only when id is absent. A non-GUID id is rejected at pack time.agentId now resolve from uipath.json#id first, then env vars (UIPATH_AGENT_ID / UIPATH_PROJECT_ID), then PROJECT_KEY. For a published agent this is the same value as before, so existing traces stay correlated.Run uipath init once in an environment that still has the project's original identity (a Studio Web project, or its .uipath/.telemetry.json) so the backfilled id matches the id Orchestrator already locked. Verify uipath.json#id equals the existing Orchestrator project id before re-publishing.
This release contains no breaking changes.
See #1695 for details.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.