[chore]: migrate to uv workspace

Merged
SE
20d ago
+3351-8132

why

  • to make managing dependencies across the monorepo easier

what changed

  • moved all python projects into a root uv workspace with a single uv.lock & .venv
  • cookbooks & integrations now use the local sdk & middleware during development
  • removed all project specific lockfiles
  • just cmds, ci/release tooling now use root workspace
  • also updates docs & contributor instructions

Summary by cubic

Migrates all Python projects to a root uv workspace with a single shared uv.lock and .venv, making dependency management across the monorepo consistent.

  • The SDK, core middleware, Deepagents integration, examples, and Python cookbooks now resolve as workspace members; per-project lockfiles were removed.
  • Cookbooks and Deepagents examples use the local SDK and middleware source during development instead of published packages.
  • just commands, CI path filters, and release tooling now run against the root workspace.
  • Preview and alpha builds pin the development SDK version across workspace consumers so they resolve in disposable checkouts.
  • The bundled Deepagents runner targets the root workspace explicitly; custom runners keep their own project environment.
  • Python cookbooks move from the pinned stagehand==4.1.0 dependency to the workspace SDK (>=4.3.0,<5), and Deepagents projects drop the <3.14 Python cap and the managed example's websockets override.

Migration

  • Run just install from the repository root; it uses pnpm install --frozen-lockfile and uv sync --all-packages --locked, replacing single-project uv sync --locked calls.