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
Report binary incompatibilities #815
Comments
I am working on this. |
@exoego I just come up with this idea too, any progress? |
I guess the idea here is that Scala Steward compares the current version and the proposed version of a dependency with MiMa but I'm wondering how useful such report would be. Imagine MiMa finds incompatibilities and Scala Steward reports them in the PR body. As receiver of this report how would you know that these incompatibilities have negative consequences for your project? Wouldn't you need to check that all your other dependencies and their transitive dependencies aren't affected by the incompatibilities? How would a human do that? I could imagine that it would make more sense that the project receiving PRs from Scala Steward uses https://github.com/scalacenter/sbt-missinglink as part of its CI which would check automatically that the project is not affected by any binary incompatibilities of the new version. |
Ah, I did not know missinglink. I initially thought mima is useful for "library", like cats or circe, which is depended by many other projects, therefore binary compatibilities is important. It seems that missinglink covers 2nd use case too. |
It would be great if Steward report binary incompatibilities on PR using https://github.com/lightbend/mima or something.
The text was updated successfully, but these errors were encountered: