Question

I’m using uv workspaces in a monorepo where the repository root pyproject.toml contains only [tool.uv.workspace] (no top-level [project]). All actual packages/apps are workspace members.

This seems to work fine in practice, but while investigating an ((un)related?) dependabot issue I learned that a workspace root without a [project] table is considered “legacy” in uv.

I can’t find clear documentation on what “legacy” implies here. Specifically:

• What is the intended / recommended model going forward: must the workspace root also be a project?
• What behavioral differences (if any) exist between:
  • workspace root with [project] vs
  • workspace root without [project]?
• Is the “legacy” workspace-only root shape slated for deprecation/removal? If so, is there a timeline or migration guidance?

Repro repository (minimal): https://github.com/jaap3/uv-workspace-dependabot/tree/ffa671b382c7d7eece7ef45b9063bfa1ef134f92
Adding a “dummy” root project: jaap3/uv-workspace-dependabot@e3f251d

Platform

Linux 6.6.87.2-microsoft-standard-WSL2 x86_64 GNU/Linux

Version

uv 0.9.29