alamb opened a new issue, #5791: URL: https://github.com/apache/arrow-rs/issues/5791
**Is your feature request related to a problem or challenge? Please describe what you are trying to do.** As part of the discussion about release cadence in https://github.com/apache/arrow-rs/issues/5368, what continually comes up is "when do we introduce breaking API changes" and "what effect does maintaining the check / discipline of avoiding the breakage have on maintainer bandwidth" Specifically, carefully evaluating all PRs to see if they have breaking API changes is non trivial and error prone, and thus increases maintenance cost. **Describe the solution you'd like** I would like to implement some sort of automated CI check that verifies semver compatibility and flags the PR appropriately if there is an API change **Describe alternatives you've considered** Perhaps we can try using one of the following crates * https://github.com/obi1kenobi/cargo-semver-checks * https://github.com/Enselic/cargo-public-api **Additional context** <!-- Add any other context or screenshots about the feature request here. --> -- 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]
