fix(deps): keep uipath and uipath-runtime ranges within one minor

[radu-mocanu]

Releases uipath-langchain 0.16.0.post1: 0.16.0's source, with two dependency ranges narrowed to the minors this build was actually released against.

-version = "0.16.0"
+version = "0.16.0.post1"
-    "uipath>=2.13.16, <2.15.0",
+    "uipath>=2.14.0, <2.15.0",
-    "uipath-runtime>=0.12.5, <0.14.0",
+    "uipath-runtime>=0.13.0, <0.14.0",

Why

0.16.0 was the release that added support for uipath 2.14 and uipath-runtime 0.13, but it widened both ceilings while leaving the old floors in place. The published ranges therefore span two minors each, and a resolver is free to pair this build with uipath-runtime 0.12 or uipath 2.13. Neither combination was released or tested against this source.

Narrowing them to a single minor makes the metadata state what the build actually supports. 0.16.2 later landed the same uipath-runtime>=0.13.0 tightening on the main line; this applies it to 0.16.0 without the source that arrived in between.

Branch

Cut from ca64d4f, the commit that built 0.16.0, per the open-source hotfix procedure. Base branch release/uipath-langchain-0.16.0 is that same commit. Not for main, which is well past 0.16.x.

Source is byte-identical to 0.16.0, which in turn is byte-identical to 0.15.2 under src/ — ca64d4f changed only dependency metadata, and the one commit between 0.15.2 and 0.15.3 was test-only. That is what makes this usable by a consumer that needs uipath-runtime 0.13.x without taking any behaviour change.

Versioning

0.16.1 and later already exist, so per the procedure this is a post-release of the version being fixed rather than a patch increment. PEP 440 orders it 0.16.0 < 0.16.0.post1 < 0.16.1, so it does not supersede anything for consumers already on a later patch.

Verification

• uv lock pinned at uipath-runtime==0.13.2, resolving uipath 2.14.1
• uv sync --locked --all-extras clean
• full test suite green, exit 0, no failures

Publishing

CD is workflow_dispatch. Dispatch it against the hotfix branch; the merge into the base branch does not trigger it.

[Copilot]

🟢 Approval recommended

Pull request overview

This PR publishes uipath-langchain as 0.16.0.post1 and corrects the dependency metadata so the declared supported ranges for uipath and uipath-runtime stay within the specific minor versions this source was built and validated against.

Changes:

• Bump package version from 0.16.0 to 0.16.0.post1 (PEP 440 post-release).
• Narrow dependency floors to uipath>=2.14.0,<2.15.0 and uipath-runtime>=0.13.0,<0.14.0.
• Update uv.lock to reflect the new metadata and the resolved uipath-runtime version (0.13.2).

File summaries

File	Description
pyproject.toml	Updates package version and tightens uipath / uipath-runtime dependency ranges.
uv.lock	Regenerates lock metadata to match the new version and dependency constraints (including resolved 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.

[radu-mocanu]

Superseded by #1058, which holds the 0.15 line instead of moving the consumer to 0.16.0. 0.16.0 is byte-identical to 0.15.3, not 0.15.2, so taking it would still have brought the guardrails BYOG change along.