-
Notifications
You must be signed in to change notification settings - Fork 902
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ensure binary compatibility for every change on CI. #554
Comments
I see we previously introduced However, usage of Wondering what's the best way forward:
|
We should re-enable japicmp for the short term, then discuss the trade-offs between the Jetbrains solution for a longer term approach. @jbarr21 You originally chose japicmp, was that only because it needed compat between a java to kt migration? |
i wasn't aware of the latter at the time & had seen other popular community libraries using japicmp, so that was the initial reasoning for going with that tool |
Going forward, I think we should use a tool such as the binary compatibility validator plugin to avoid making unconscious binary-incompatible changes to the library API.
The text was updated successfully, but these errors were encountered: