The 0.3.0 sdist's `pyproject.toml` sets `[build-system] requires = ["scikit-build-core >= 0.10", ...]` but `[tool.scikit-build] cmake.minimum-version = "3.15"`. scikit-build-core >= 0.8 removed that key in favour of `cmake.version` and now hard-errors at the "Getting requirements to build wheel" step:
```
ERROR: Use cmake.version instead of cmake.minimum-version with scikit-build-core >= 0.8
```
Since the declared floor (>= 0.10) is already past the point where the old key is rejected, every scikit-build-core version that satisfies the floor fails, on any platform/architecture — there is no working combination once a fresh build environment resolves scikit-build-core "from the sdist" (only the 0.3.0 tag has this, presumably because an older scikit-build-core happened to still be current when it was released). This means `pip install sparsediffpy==0.3.0` fails to build from source wherever no prebuilt wheel exists (confirmed on linux/aarch64 with no other changes).
Reproduction:
```
pip install --no-binary sparsediffpy sparsediffpy==0.3.0
```
Fix is a one-line `pyproject.toml` change:
```diff
[tool.scikit-build]
-cmake.minimum-version = "3.15"
+cmake.version = ">=3.15"
```
We ran into this while adding riscv64 wheels for `sparsediffpy` (and transitively for `cvxpy`, which pins `sparsediffpy>=0.3.0,<0.4.0`) at https://github.com/riseproject-dev/python-wheels — happy to send a PR with the one-line fix if useful.
The 0.3.0 sdist's `pyproject.toml` sets `[build-system] requires = ["scikit-build-core >= 0.10", ...]` but `[tool.scikit-build] cmake.minimum-version = "3.15"`. scikit-build-core >= 0.8 removed that key in favour of `cmake.version` and now hard-errors at the "Getting requirements to build wheel" step:
```
ERROR: Use cmake.version instead of cmake.minimum-version with scikit-build-core >= 0.8
```
Since the declared floor (>= 0.10) is already past the point where the old key is rejected, every scikit-build-core version that satisfies the floor fails, on any platform/architecture — there is no working combination once a fresh build environment resolves scikit-build-core "from the sdist" (only the 0.3.0 tag has this, presumably because an older scikit-build-core happened to still be current when it was released). This means `pip install sparsediffpy==0.3.0` fails to build from source wherever no prebuilt wheel exists (confirmed on linux/aarch64 with no other changes).
Reproduction:
```
pip install --no-binary sparsediffpy sparsediffpy==0.3.0
```
Fix is a one-line `pyproject.toml` change:
```diff
[tool.scikit-build]
-cmake.minimum-version = "3.15"
+cmake.version = ">=3.15"
```
We ran into this while adding riscv64 wheels for `sparsediffpy` (and transitively for `cvxpy`, which pins `sparsediffpy>=0.3.0,<0.4.0`) at https://github.com/riseproject-dev/python-wheels — happy to send a PR with the one-line fix if useful.