Skip to content

0.5.0
Compare
Choose a tag to compare
@dwijnand dwijnand released this 12 Jul 15:47
0.5.0
This tag was signed with the committer’s verified signature.
dwijnand Dale Wijnand
GPG key ID: 4F256E3D151DF5EF
Learn about vigilant mode.
b443945
This commit was signed with the committer’s verified signature.
dwijnand Dale Wijnand
GPG key ID: 4F256E3D151DF5EF
Learn about vigilant mode.

Fixing the impact of 0.4.0's breaking change

The 0.4.0 release of MiMa included a breaking change that sought to help users discover when they were running mimaReportBinaryIssues but hadn't configured mimaPreviousArtifacts.

Unfortunately, that had a larger impact than expected, quickly brought to light thanks to the PRs sent by the ScalaSteward (see the ScalaSteward annoucement blog post!).

With the release of MiMa 0.5.0 we've been able to solve the initial issue by being able to differentiate when mimaPreviousArtifacts was unset by the user and when it was purposely set to the empty set (for instance, if their library cross-builds to Scala 2.13 but hasn't yet been released for Scala 2.13).

Additionally the README has been fully refreshed and now gives better guidance, in particular see the Setting different mimaPreviousArtifacts and Make mimaReportBinaryIssues not fail sections, the latter of which details how use 0.4.0's mimaFailOnNoPrevious setting to handle breakages.

#328/#334/#338

Additional improvements

  • Fix resolving previous artifacts that defined their Scala version suffix. #327/#329

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

Assets 2
Loading