Repository navigation
fix(templates): drop exclude-newer from the template uv.lock and add default input values - #385
Merged
Conversation
There was a problem hiding this comment.
🟢 Approval recommended
No active review issues were identified in the template configuration and lockfile changes.
No open issues 🎉
What changed in this PR
Fixes locked environment preparation for scaffolded LlamaIndex agents by keeping repository-only exclude-newer settings out of template locks. Adds the same safeguard to the Claude SDK template for future lock generation.
Changes:
- Adds empty
[tool.uv]tables to both templates to stop parent configuration discovery, with comments explaining why they must remain. - Removes inherited cooldown options from the LlamaIndex template lock without changing any pinned versions.
| File | Description |
|---|---|
packages/uipath-llamaindex/template/uv.lock |
Removes inherited exclude-newer options so locked installs work outside the repository. |
packages/uipath-llamaindex/template/pyproject.toml |
Adds a documented configuration boundary to prevent cooldown inheritance. |
packages/uipath-claude-sdk/template/pyproject.toml |
Adds the same boundary to protect future template locks. |
Review effort: Balanced
vldcmp-uipath
force-pushed
the
fix/template-lock-without-exclude-newer
branch
6 times, most recently
from
November 19, 2026 11:44
18d7e9e to
953eb6f
Compare
…default input values The templates have no [tool.uv] table, so uv kept walking up to the package root and locked the llamaindex template under its `exclude-newer = "2 days"`. That setting ended up in template/uv.lock's [options]. A scaffolded project is synced outside this repo, where the setting does not exist, and `uv sync --locked` then fails with "Resolving despite existing lockfile due to removal of global exclude newer ... needs to be updated". The Robot adds --locked whenever a uv.lock is present and runs uv with UV_NO_CONFIG=1, so every project started from the template since the lock was regenerated fails to prepare its environment. An empty [tool.uv] table stops the parent search. The llamaindex lock is regenerated from the committed one; the only change is the removal of the [options] block, every pinned version stays. The claude-sdk template ships no lock yet, so it only gets the table, which keeps a future `uv lock` from reintroducing the setting. The other packages have no template directory. Each sample's input also gets a default so Studio Web can prefill the field: llamaindex `question` and claude-sdk `city` default to the example from their descriptions. With a default the field is optional, so each entry-points.json carries the default on the property and no longer lists it under required, which is the schema `uipath init` emits for this declaration. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014t9fy8viiGwocCpYNyc7uq
vldcmp-uipath
force-pushed
the
fix/template-lock-without-exclude-newer
branch
from
November 19, 2026 14:55
953eb6f to
5c551fc
Compare
|
radu-mocanu
approved these changes
Nov 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



What changed
Every coded agent scaffolded from
packages/uipath-llamaindex/template/since its lock was last regenerated fails to prepare its environment:The template
pyproject.tomlfiles have no[tool.uv]table, so whenuv lockruns inside this repo uv walks up to the package root and applies itsexclude-newer = "2 days"plus theexclude-newer-packageexemptions. uv records that in the template'suv.lockunder[options]. A scaffolded project lives outside this repo, where the setting does not exist. uv treats the mismatch as a stale lock, re-resolves, and--lockedrefuses the result. The Robot adds--lockedwhenever auv.lockis present and runs uv withUV_NO_CONFIG=1, so even a[tool.uv]in the project could not satisfy it there.packages/uipath-llamaindex/template/pyproject.toml: adds an empty[tool.uv]table. uv stops the parent search at the firstpyproject.tomlthat has the table, so the package's cooldown no longer reaches the template. It is deliberately uncommented, because Studio Web ships this file verbatim as the sample'spyproject.toml.packages/uipath-llamaindex/template/uv.lock: regenerated from the committed lock withuv lock(no--upgrade). The diff is the removal of the[options]block only. Every pinned version is unchanged.packages/uipath-claude-sdk/template/pyproject.toml: the same empty table. This template ships no lock today, so nothing fails there, but a futureuv lockrun inside the repo would reintroduce the problem without it.main.pyandentry-points.jsonin both templates: the input gets a default so Studio Web can prefill the field. llamaindexquestiondefaults to "What's the weather in Paris?" and claude-sdkcityto "London", the examples already in their descriptions. With a default the field is optional, so eachentry-points.jsoncarriesdefaulton the property and no longer lists the field underrequired, which is the schemauipath initemits for this declaration. Descriptions are unchanged.Checked the rest of the repo:
uipath-agent-framework,uipath-google-adk,uipath-openai-agentsanduipath-pydantic-aihave notemplate/directory, theiruipath newscaffolds copy nouv.lock, and no sample ships a lock. The locks undertestcases/carry noexclude-newer. Each package root keeps its own cooldown, so package locking is unaffected.How it was tested
uv 0.11.32.
uv lock --checkreports "removal of global exclude newer", confirming the table stops the inheritance.uv lock --checkpasses in place.uv lock --checkpasses, with and withoutUV_NO_CONFIG=1, andUV_NO_CONFIG=1 uv sync --locked --no-dev --dry-runresolves without re-locking. Before this change the same copy failed with the error above.model_json_schema()with the default in place produces the input schemas committed in bothentry-points.jsonfiles:defaulton the property, norequiredlist. The claude-sdk output schema is untouched.Follow-ups
UiPath/Agents(UiPath/Agents#7080 carries the resync). Once this merges,pnpm sync:coded-agent-templatesthere againstmainyields identical content with the merge SHA in the header. Projects already created from the current template need a one-timeuv lockby their owners.uv addruns, it has to live in the template'spyproject.tomland in the lock together, and the Robot has to read the project's[tool.uv]under a managed decision or sync with--frozen. That is a separate conversation with the Robot team.🤖 Generated with Claude Code
https://claude.ai/code/session_014t9fy8viiGwocCpYNyc7uq