sm new sample module pins simple_module_core/db/hosting>=1.0,<2.0 — uv sync fails because framework is at 0.0.x

[antosubash]

Summary

The modules/hello/ sample module that sm new (in simple_module_cli==0.0.8) now generates pins its framework deps to a 1.x range, but the framework is at 0.0.x. uv sync fails immediately on a fresh scaffold with an unsatisfiable workspace.

Reproduction

$ uvx --from simple_module_cli sm new my-app --db sqlite --preset standard -y --no-install
$ cd my-app && cp .env.example .env
$ make install
uv sync
Using CPython 3.12.10
Creating virtual environment at: .venv
 × No solution found when resolving dependencies:
 ╰─▶ Because simple-module-chat depends on simple-module-hosting==0.0.8
 and simple-module-hello depends on simple-module-hosting>=1.0,<2.0,
 we can conclude that simple-module-chat and simple-module-hello are
 incompatible.
 And because your workspace requires simple-module-chat and
 simple-module-hello[dev], we can conclude that your workspace's
 requirements are unsatisfiable.
make: *** [install] Error 1

Root cause

modules/hello/pyproject.toml (generated):

[project]
name = "simple_module_hello"
...
dependencies = [
 "simple_module_core>=1.0,<2.0",
 "simple_module_db>=1.0,<2.0",
 "simple_module_hosting>=1.0,<2.0",
 ...
]

[project.optional-dependencies]
dev = [
 ...
 "simple_module_test>=0.1,<1.0",
]

But on PyPI, simple_module_core (and friends) are at 0.0.8. simple_module_test is at 0.0.8 too. The host's own pyproject.toml correctly pins ==0.0.8. So the host says "I want 0.0.8" and hello says "I want 1.x" — uv can't satisfy both.

simple_module_test>=0.1,<1.0 is also unsatisfiable: 0.0.8 is not >=0.1.

The framework's own modules in modules/auth/pyproject.toml (in the source tree) use simple_module_core==0.0.7 style exact pins, so the working pattern exists — the scaffold template just used the wrong shape.

Suggested fix

The scaffold template for modules/<name>/pyproject.toml should pin to a range that includes the framework's current published version. Two cleanly-shaped options:

1. Match the host scaffold's exact-pin style. Have sm new substitute its own version in for both the host pins AND the sample module pins:

   dependencies = [
    "simple_module_core=={cli_version}",
    "simple_module_db=={cli_version}",
    "simple_module_hosting=={cli_version}",
    "pydantic-settings>=2.0",
    "sqlalchemy>=2.0",
   ]

2. Use [tool.uv.sources] workspace pins for the sample. Since the host's pyproject.toml already does this for simple_module_hello:

   [tool.uv.sources.simple_module_hello]
   workspace = true

   The sample module itself could declare loose ranges (>=0.0.1) and rely on the host's exact pin to constrain the resolution.

Either way, the dev dep should also be fixed:

- "simple_module_test>=0.1,<1.0",
+ "simple_module_test>=0.0.8,<0.1",

Suggested test

Add a CLI regression that runs sm new into a tmpdir and runs uv sync against it. Should pass without manual intervention.

Workaround

Edit modules/hello/pyproject.toml:

 dependencies = [
- "simple_module_core>=1.0,<2.0",
- "simple_module_db>=1.0,<2.0",
- "simple_module_hosting>=1.0,<2.0",
+ "simple_module_core>=0.0.8,<0.1",
+ "simple_module_db>=0.0.8,<0.1",
+ "simple_module_hosting>=0.0.8,<0.1",
 ...
 ]
 ...
- "simple_module_test>=0.1,<1.0",
+ "simple_module_test>=0.0.8,<0.1",

Related

• sm new should scaffold host + a working sample module in a uv/npm workspace, matching the framework repo's own layout #117 — the sample module exists at all (this is the new scaffold output mentioned there).
• sm new scaffold pins ^0.0.3 npm deps and ==0.0.7 python deps even when 0.0.8 is published; npm caret on 0.0.x silently blocks the bump #119 — version-pin staleness in the scaffold's host templates. Same family of bug, different file.

Environment

• simple_module_cli 0.0.8
• simple_module_core, simple_module_db, simple_module_hosting, simple_module_test all at 0.0.8 on PyPI

[antosubash]

Fixed in #130.

[antosubash]

Verified in 0.0.10. modules/hello/pyproject.toml now pins simple_module_core==0.0.10, simple_module_db==0.0.10, simple_module_hosting==0.0.10 (and simple_module_test==0.0.10 in dev). uv sync --all-packages resolves cleanly.