Should breaking change in PR #1200 raise error instead of emitting warning?

[bradday4]

The breaking change in #1200 for python package metadata in cargo.toml is emitted as a warning instead of an error. i.e the build system continues despite the fact that python dependencies will not be incorporated into the project. I know of 1 project where this has caused a bad build artifact from their CI/CD pipeline bed-reader . Wouldn't it be better to have Maturin raise an exception instead of continuing the build process if cargo.toml still defines these keys?

[messense]

Implemented in #1471.

bed-reader should add a version constraint in https://github.com/fastlmm/bed-reader/blob/46ece2e6efd1fb8f5a9335fd8b3ef7a3d711b9fa/.github/workflows/ci.yml#L60, same as https://github.com/fastlmm/bed-reader/blob/46ece2e6efd1fb8f5a9335fd8b3ef7a3d711b9fa/pyproject.toml#L20