Repository navigation
chore: bump the llamaindex template to 0.6.2 and align claude-sdk's uipath pins - #376
Conversation
There was a problem hiding this comment.
🟢 Approval recommended
The focused configuration changes are consistent with the scaffold update, with no blocking issues identified.
No open issues 🎉
What changed in this PR
Updates Studio Web’s LlamaIndex sample scaffold to the 0.6.2 dependency range, matching the CLI-generated scaffold.
Changes:
- Raises the template dependency range to
>=0.6.2, <0.7.0. - Exempts
uipath-llamaindexfrom the two-day release cutoff and records the exemption in the package lockfile.
| File | Description |
|---|---|
packages/uipath-llamaindex/uv.lock |
Records the release-cutoff exemption. |
packages/uipath-llamaindex/template/pyproject.toml |
Updates the scaffold dependency range. |
packages/uipath-llamaindex/pyproject.toml |
Allows same-day uipath-llamaindex releases. |
Review effort: Balanced
…e-lock it The `template/` project that Studio Web embeds as its "Start with sample" scaffold still depended on `uipath-llamaindex[bedrock,vertex]>=0.5.11, <0.6.0` and locked 0.5.11 (uipath 2.10.43, uipath-dev 0.0.78). Move it to `>=0.6.2, <0.7.0`, the same range `uipath new` scaffolds since ffa4e6b, and re-lock with `uv lock --upgrade`: uipath-llamaindex 0.6.2, uipath 2.14.41, uipath-platform 0.2.40, uipath-runtime 0.13.5, uipath-dev 0.0.86. The template inherits the package's `exclude-newer = "2 days"` policy, which filtered out the 0.6.2 release published today. Opt uipath-llamaindex itself out of that filter alongside the other first-party packages; the package's own uv.lock only records the new option entry. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LXV7PuGNNCdLKQomjoH1M4
1774f54 to
b130cfc
Compare
uipath-claude-sdk still allowed any uipath 2.14.x and locked 2.14.1. The other integrations moved to >=2.14.41 in 9795cbf, the first release that sends AgentFramework on coded run events; align this package with them and re-lock (uipath 2.14.41, uipath-core 0.5.33, uipath-platform 0.2.40, uipath-runtime 0.13.5). Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LXV7PuGNNCdLKQomjoH1M4
|
|
Two samples in this repo still resolve below what the next Robot release accepts (
Packed as they are, they fail on a local Robot with |
|
One more in this repo: The Robot's minimum-version check asks for This PR raises claude-sdk's |



Two commits.
uipath-llamaindex template (the Studio Web "Start with sample" scaffold)
template/pyproject.toml:uipath-llamaindex[bedrock,vertex]>=0.6.2, <0.7.0(was>=0.5.11, <0.6.0), matching theuipath newscaffold.template/uv.lock: re-locked to uipath-llamaindex 0.6.2, uipath 2.14.41, uipath-dev 0.0.86.pyproject.toml: optsuipath-llamaindexout of the inheritedexclude-newer = "2 days"filter, like the other first-party packages, so the template can resolve a same-day release. Packageuv.lockonly records the option.uipath-claude-sdk
uipath>=2.14.41, <2.15.0(was>=2.14.0), aligning with the other integrations after 9795cbf.uv.lock: uipath 2.14.41, uipath-core 0.5.33, uipath-platform 0.2.40, uipath-runtime 0.13.5. No package version bump, same as 9795cbf.The
uipath-runtime>=0.13.5bump for claude-sdk reached this branch after the merge and is in #379.Tested: llamaindex template syncs and
main.pyimports against 0.6.2; llamaindex and claude-sdk test suites pass; ruff clean.Companion PRs: UiPath/Agents#6733, UiPath/uipath-langchain-python#1169.
🤖 Generated with Claude Code
https://claude.ai/code/session_01LXV7PuGNNCdLKQomjoH1M4