You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: remove lockfile fallback for remote templates (#255)
Removes the behavior of falling back to a base lockfile if the remote template does not contain one.
This is a breaking change for remote templates that were relying on the fallback behavior.
With this change:
- If a remote template has a file, it's copied over.
- If it does not, no is created, and the user is expected to generate one.
The documentation has been updated to reflect this new behavior.
Copy file name to clipboardExpand all lines: docs/guide/remote-templating.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -134,8 +134,8 @@ You have full control over the Python dependencies. Both `pyproject.toml` and `u
134
134
* **`pyproject.toml`**: Required file that replaces the base template's version. Must include all dependencies for your agent.
135
135
136
136
* **`uv.lock`**: Strongly recommended to ensure reproducibility.
137
-
* If present, guarantees exact dependency versions.
138
-
* If missing, falls back to base template's lock file. A new lock file will be generated by the user when performing installation.
137
+
* If present, it will be copied to the generated agent, guaranteeing exact dependency versions.
138
+
* If missing, the generated agent will **not** include a `uv.lock` file. The user is expected to generate one by running `make install` or `uv pip sync` after the agent is created.
139
139
140
140
**Best Practice:** Always run `uv lock` after changing dependencies and commit the resulting lock file.
0 commit comments