Skip to content

0.7.0

Compare
Choose a tag to compare
@dwijnand dwijnand released this 28 Feb 08:31
0.7.0

Features

  • Checking generic signatures is now opt-in. #471

Most MiMa checks (DirectMissingMethod, IncompatibleResultType, IncompatibleMethType, etc) are against the method descriptor, which is the "raw" type signature, without any information about generic parameters.
The IncompatibleSignature check compares the Signature, which includes the full signature including generic parameters. This can catch real incompatibilities, but also sometimes triggers for a change in generics that
would not in fact cause problems at run time. Notably, it will warn when updating your project to scala 2.12.9+ or 2.13.1+, see #423 ("Signature checks fail using value classes & upgrading to 2.12.9+ or 2.13.1+") for details.

This check is now disabled by default. You can opt-in to it by setting:

ThisBuild / mimaReportSignatureProblems := true

Improvements

  • Improve problem reporting (#475), specifically, it now:
    • logs at the appropriate log level (warn/error, if there are problems/fatal problems)
    • includes the version of the artifact compared against
    • includes the number of filtered out problems

Bugfixes

  • Fix a regression in how version filtered are... filtered. #468

Other changes

  • Drop Bintray, switch releasing the plugin to Maven Central. #469

For full details see the milestone and/or the changelog.