"Bug fix" in maturin causing "project.version field is required" error

[andrewnguonly]

Heads up. This issue in maturin may impact future builds: PyO3/maturin#2416

A fix was merged a few hours ago: PyO3/maturin#2417

Error:

#15 70.10   💥 maturin failed
#15 70.10     Caused by: `project.version` field is required in pyproject.toml unless it is present in the `project.dynamic` list
#15 70.10   Error: command ['maturin', 'pep517', 'build-wheel', '-i', '/tmp/tmp9wkq8uoa/.venv/bin/python', '--compatibility', 'off'] returned non-zero exit status 1
#15 70.10   
#15 70.10 
#15 70.10   at /usr/local/lib/python3.11/site-packages/poetry/installation/chef.py:147 in _prepare
#15 70.11       143│ 
#15 70.11       144│                 error = ChefBuildError("\n\n".join(message_parts))
#15 70.11       145│ 
#15 70.11       146│             if error is not None:
#15 70.11     → 147│                 raise error from None
#15 70.11       148│ 
#15 70.11       149│             return path
#15 70.11       150│ 
#15 70.11       151│     def _prepare_sdist(self, archive: Path, destination: Path | None = None) -> Path:
#15 70.11 
#15 70.11 Note: This error originates from the build backend, and is likely not a problem with poetry but with jsonschema-rs (0.18.3) not supporting PEP 517 builds. You can verify this by running 'pip wheel --use-pep517 "jsonschema-rs (==0.18.3)"'.
#15 70.11 
#15 ERROR: process "/bin/sh -c pip3 install poetry==\"$POETRY_VERSION\" &&     poetry config virtualenvs.create false &&     poetry install --without dev,test --no-interaction --no-ansi --no-root --no-directory &&     python -c \"import compileall; compileall.compile_path(maxlevels=1000, legacy=True)\"" did not complete successfully: exit code: 1

[Stranger6667]

Hi @andrewnguonly

Thanks for the heads up! Recently I experienced a similar issue with uv complaining about the absence of version or dynamic = ["version"]. Hence I've added the latter and the issue was resolved. From the logs you've provided I see that the jsonschema version is not the latest one - 0.18.3. Could you, please, check if the issue is still there for 0.28.0?