fix(deps): allow uipath-runtime 0.13.x on the 2.13 line - #1876
fix(deps): allow uipath-runtime 0.13.x on the 2.13 line#1876radu-mocanu wants to merge 1 commit into
Conversation
Widens the ceiling only: uipath-runtime>=0.12.2,<0.13.0 -> <0.14.0. No source change. Every release on the 2.13 line caps uipath-runtime below 0.13.0, so a consumer that stays on this line cannot install uipath-runtime 0.13.x at all. Published metadata is immutable, so lifting the cap needs a new release on the line rather than an edit to 2.13.22. Cut from c9b2428, the commit that built 2.13.22.
There was a problem hiding this comment.
🟢 Approval recommended
Pull request overview
This PR cuts a patch release on the uipath 2.13.x line to widen the uipath-runtime dependency upper bound so environments pinned to 2.13.x can resolve and install uipath-runtime 0.13.x.
Changes:
- Bump
uipathversion from2.13.22to2.13.23. - Widen
uipath-runtimerequirement from<0.13.0to<0.14.0. - Update
uv.lockto reflect the new constraint and pinuipath-runtime==0.13.2.
File summaries
| File | Description |
|---|---|
| packages/uipath/pyproject.toml | Version bump and widened uipath-runtime upper bound to allow 0.13.x on the 2.13 release line. |
| packages/uipath/uv.lock | Lockfile updated to match the new constraint and to pin uipath-runtime to 0.13.2 for CI/verification. |
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.
|
Closing: not needed, and not implementable under the single-minor range rule. Making the 2.13 line accept The consumer moves to 2.14.1 instead, which is the first published release admitting 0.13.x in a single-minor range. No release is needed on the 2.13 line. |
Releases
uipath2.13.23 from the 2.13 line with a single dependency-requirement change.Why
Every release on the 2.13 line caps
uipath-runtimebelow 0.13.0, and 2.14.0 is the first release that widened it. A consumer that has to stay on the 2.13 line therefore cannot installuipath-runtime0.13.x at all: there is exactly oneuipath-runtimein an environment, and 0.13.2 does not satisfy<0.13.0, so resolution is unsatisfiable.Published metadata is immutable, so the cap cannot be lifted by editing 2.13.22. It needs a new release on the line, which is why this exists. The source is byte-identical to 2.13.22.
Branch
Cut from
c9b2428a, the commit that built 2.13.22, per the open-source hotfix procedure. Base branchbase/uipath-2.13.xis that same commit. Not formain, which is already on 2.14.x.Verification
uv lockinpackages/uipathpinned atuipath-runtime==0.13.2uv sync --locked --all-extrascleanpackages/uipathsuite green againstuipath-runtime0.13.2, exit 0, no failuresThe lockfile is pinned at 0.13.2 rather than the newest 0.13.x so CI exercises the exact runtime this widening is being requested for.
Publishing
CD is
workflow_dispatch, so dispatch it against the hotfix branch after merge. 2.13.23 is free on PyPI, so this is a patch increment rather than a post-release.