fix(deps): move the uipath-runtime range to 0.13 on the 2.13 line

[radu-mocanu]

Releases uipath 2.13.23: 2.13.22's source with one dependency range moved.

-version = "2.13.22"
+version = "2.13.23"
-  "uipath-runtime>=0.12.2, <0.13.0",
+  "uipath-runtime>=0.13.0, <0.14.0",

Why

Every published release on the 2.13 line caps uipath-runtime below 0.13.0, and 2.14.0 is the first release that moved past it. A consumer that has to stay on this line therefore cannot reach uipath-runtime 0.13.x at all: there is one uipath-runtime in an environment, and 0.13.x does not satisfy <0.13.0, so resolution is unsatisfiable.

Published metadata is immutable, so the range cannot be corrected by editing 2.13.22. It needs a new release on the line, which is what this is.

Note that the range moves rather than widens. >=0.12.2, <0.14.0 would span two minors and let a resolver pair this build with either runtime generation; >=0.13.0, <0.14.0 states exactly one.

Compatibility

The source is unchanged from 2.13.22, and it was never released against uipath-runtime 0.13.x, so that pairing is verified by running it rather than by a prior release: the full packages/uipath suite passes against 0.13.2, exit 0, no failures.

Branch

Cut from c9b2428a, the commit that built 2.13.22, per the open-source hotfix procedure. Base branch is that same commit. Not for main, which is on 2.14.x.

The base branch is named base/uipath-2.13.22 rather than release/uipath-2.13.22 only because the release/* namespace is covered by the Actions ruleset, which requires a pull request for any update and so blocks creating the branch at all. The earlier 2.11.19 hotfix used a non-release prefix for the same reason. Happy to move it if someone with bypass creates the release/ branch.

Versioning

2.13.22 is the latest release on the line and 2.13.23 is free on PyPI, so this is a patch increment rather than a post-release.

Verification

• uv lock in packages/uipath pinned at uipath-runtime==0.13.2
• uv sync --locked --all-extras clean
• full packages/uipath suite green against 0.13.2

The lockfile is pinned at 0.13.2 rather than the newest 0.13.x so CI exercises the exact runtime this release is cut for.

Publishing

CD is workflow_dispatch, and detect_publishable_packages.py publishes any version that 404s on PyPI, reading whatever ref the run checked out. Dispatch it against this hotfix branch; merging into the base branch triggers nothing.

[Copilot]

🟢 Approval recommended

Pull request overview

This PR prepares the uipath package for a 2.13.x hotfix release that moves the uipath-runtime dependency range to the 0.13 minor line, allowing consumers pinned to uipath==2.13.* to resolve uipath-runtime 0.13.x.

Changes:

• Bump uipath package version from 2.13.22 → 2.13.23.
• Update uipath-runtime dependency constraint from >=0.12.2,<0.13.0 → >=0.13.0,<0.14.0 (move, not widen).
• Refresh uv.lock to reflect the updated constraint and pin uipath-runtime to 0.13.2.

File summaries

File	Description
packages/uipath/pyproject.toml	Bumps package version and moves the uipath-runtime dependency range to 0.13.*.
packages/uipath/uv.lock	Updates locked metadata to match 2.13.23 and pins uipath-runtime==0.13.2.

Review details

• Files reviewed: 1/2 changed files
• Comments generated: 0
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.