sunng87 opened a new issue, #3876: URL: https://github.com/apache/arrow-rs/issues/3876
**Describe the bug** When we add arrow-flight as a dependency to a project that already has `prost-build` as a build-dependency, there is a big chance that cargo will fail to select a valid version of `prost-build` and it cause build failure. The reason is we are using pinned versions of `prost-build`. When the project has a newer patch version for `prost-build`, for example, updated by dependabot, the pinned version will conflict with project's requirement for `prost-build`. **To Reproduce** This happens to any project that: - has `prost-build` as build-dependency, with version "0.11.8" - adds `arrow-flight` 35 as dependency, which pins `prost-build` to "0.11.7" - cargo build: conflict. **Possible solutions** There are some proposals to consider: - simply relax the pin - don't check in generated sources - use pinned prost-build as dev-dependency and generate the code via script or ci -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
